Closed tangobravo62 closed 3 years ago
Probably fixed with CLI 0.5.2 (commit e4b80a8). Test evidence to be added.
Fully fixed now:
prosEO (PTM)> productclass rule update PTM_L3
[ 1] FOR PTM_L2B SELECT ValIntersect(2 H, 7 M) MINCOVER(90)
(Mode: OPER, configured processors: [PTML3_0.1.0_OPER_2020-03-25])
[ 2] FOR PTM_L2A SELECT ValIntersect(0 D, 0 D) MINCOVER(90)
(Mode: OPER, configured processors: [PTML3_0.1.0_OPER_2020-03-25])
Select rule (empty field cancels): 1
Selection rule in Rule Language (empty field cancels, ^D terminates):
FOR PTM_L2B SELECT ValIntersect(0,0) mincover(50)
(I2876) Selection rule with database ID 55 updated (new version 4)
prosEO (PTM)> productclass rule show PTM_L3
ID: 55
FOR PTM_L2B SELECT ValIntersect(0 D, 0 D) MINCOVER(50)
(Mode: OPER, configured processors: [PTML3_0.1.0_OPER_2020-03-25])
ID: 57
FOR PTM_L2A SELECT ValIntersect(0 D, 0 D) MINCOVER(90)
(Mode: OPER, configured processors: [PTML3_0.1.0_OPER_2020-03-25])
Updating a selection rule through the CLI does not work, neither from prompt nor from file: (1) From prompt: No prompt for rule entry given:
(2) From file:
Input file contains the lines:
It was expected that both rules get replaced, not only one. Perhaps clarification of the help text is needed.
Removing the second selection rule from the file results in an error:
Log excerpt for ProductClassManager: