...
Many plugins have fields (configurable properties) that are used in constructing or validating a schema at configure time. These fields need to have macros disabled to allow this. The following plugins and fields would be affected:
| Plugin | Fields | NotesUse | Conflict | |
|---|---|---|---|---|
| BatchCassandraSource | schemaThe | schema is parsed Parsed for correctness to create the schema.RealtimeCassandraSink | addresses | Addresses are parsed at configure time. Parsing aParsing a macro or schema with a nested macro would fail. |
| CopybookSource | copybookContents | Copybook contents are converted to an InputStream and used to get external records, which are in turn used to add fields to the schema. | Schema would add macro literal as a field. | |
| DedupAggregator | uniqueFields, filterOperation | Both fields are used to validate the input schema created. | Macro literals do not exist as fields in schema and will throw IllegalArgumentException | |
| DistinctAggregator | fields | Used to specify the fields used to construct the output schema. | Will add macro literals as schema fields.* | |
| GroupByAggregator | groupByFields, aggregates, |
* May need verification
Other plugins have fields that are validated/processed at configure time that do not affect the schema. In these cases, these can be moved to initialization time. The following plugins and fields would be affected:
| Plugin | Fields | Use |
|---|---|---|
* May need verification
Setting Hydrator runtime arguments using CDAP runtime arguments/preferences
...