[Feature Request]: extended metadata annotations for `@Transform`, `@Action` and `@HopMetadataProperty`

[bamaer]

What would you like to happen?

additional metadata will help to identify if a @Transform or @Action works on files, databases (relational and NoSQL), is input/output etc.
on the property level, additional metadata information can provide information if a @HopMetadataProperty works on files, relational database tables/columns etc.

Suggested changes:

• add a new @ActionTransformType annotation that indicates the purpose for an action or transform. Possible values in the enum could include (not exhaustive):
  • INPUT
  • OUTPUT
  • FILE
  • RDBMS
  • GRAPH
  • NOSQL
• extend HopMetadataProperty with a new metadata property type that is an array of a new HopMetadataPropertyType enum. Possibile initial values in this enum could include (not exhaustive):
  • FILE_PATH
  • FILE_NAME
  • FILE_WILDCARD
  • FILE_ENCODING
  • FILE_FIELD
  • FILE_SEPARATOR
  • FILE_ENCLOSURE
  • FILE_EXTENSION,
  • RDBMS_SCHEMA
  • RDBMS_TABLE
  • RBMS_COLUMN
  • RDBMS_SQL
  • RDBMS_TRUNCATE
  • RDBMS_SQL_SELECT
  • RDBMS_SQL_INSERT
  • RDBMS_SQL_UPDATE
  • RDBMS_SQL_DELETE
  • RDBMS_SQL_BULK
  • GRAPH_QUERY
  • GRAPH_NODE
  • GRAPH_RELATIONSHIP

Issue Priority

Priority: 3

Issue Component

Component: Actions, Component: Metadata, Component: Transforms

[bamaer]

.take-issue