Add DatasetDiscovery annotation :
Add a base class for DatasetDiscovery configuration to inherit from with boolean property to check if user wants the dataset to be returned.
Modify DatasetValidator so that it allow a Emitter class to have a Dataset OR a DatasetDiscovery attribute.
- Ability to create new @DatasetDiscovery kind of configuration
- Retrieve those kind of configuration thanks to a rest call to the component server
- Having validation that force @DatasetDiscovery having a nested @Datastore + normal validation (should be same validation that for @Dataset + inheritance of DatasetDiscoveryConfiguration that contain 1 mandatory option)
- Using @DatasetDiscovery in a mapper/input connector
The feature is "Ready" when all DoR check marks are
Possible status of the checkmarks:
- ready, complete
- missing some information
- not started to complete
|Is the user-story properly defined?
|Are they defined? Were they validated by PO, Dev and QA?
|Is the Jira information correct? (fix version, labels, security level)
Reachable for QA/Doc/automation(TTP, Junit)
|Is license EE or SE clearly identified ?
|Does the developer understand how it will be implemented?
Do we have a solution?
Approved/discussed with architecture (in-team, global or security, depending on the scope)?
|Are all dependencies linked to JIRA (link "depends on")?
Are they done?
|Is migration needed?
|Is DOCT created and linked under the epic?
Not DOCT but has to update TCK documentation to be visible in tck web site.
|Is slack feat- created? With all the correct owner involved? (QA/Doc/PO/SM) : #eng-dataset-discovery
|Are there changes in the UI & were they added in the DOCT?
For new forms, was it approved by UX?
For new connectors, was a TUX ticket created for a new Icon?