bamaer opened a new issue, #8815:
URL: https://github.com/apache/hop/issues/8815

   ### Apache Hop version?
   
   2.20.0-SNAPSHOT
   
   ### Java version?
   
   21
   
   ### Operating system
   
   macOS
   
   ### What happened?
   
   ### What happened
   
   `RuleTargetFields` offers the fields below for rules, and `hop lint 
--list-fields` and the rule editor show them, but `CustomRuleExecutor` resolves 
none of them. A rule written against one of them never fires, and nothing tells 
the rule's author why.
   
   | Target | Fields that never resolve |
   |---|---|
   | `DATABASE_CONNECTION` | `databaseType`, `servername`, `dataTablespace`, 
`indexTablespace`, `attributes`, `connectionPoolingParameters`, 
`partitioningInformation`, `maxConnectionPoolSize`, `initialPoolSize` |
   | `TRANSFORM` | `errorHandling`, `targetTransforms`, `distributes`, 
`location`, `selected` |
   | `ACTION` | `errorHandling`, `targetActions`, `location`, `selected` |
   
   For connections they fall through to the default branch, log "Unknown 
database field" at detailed level and return `null`. For transforms and actions 
they are looked up by reflection on the plugin's metadata class, which has no 
such field.
   
   ### Expected
   
   Every field that is offered resolves, or is no longer offered. In particular:
   
   - `DATABASE_CONNECTION.databaseType`: the database plugin id (e.g. 
`POSTGRESQL`).
   - `DATABASE_CONNECTION.attributes`: the connection's attributes, including 
its extra options.
   - `TRANSFORM.errorHandling`: true when error handling is configured for the 
transform.
   
   ### How to reproduce
   
   A rule on `DATABASE_CONNECTION` with `targetField: databaseType`, 
`condition: NOT_EMPTY` reports nothing for any connection, although every 
connection has a type.
   
   ### Issue Priority
   
   Priority: 2
   
   ### Issue Component
   
   Component: Hop Gui, Component: Metadata


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to