This message was deleted.

Hi Siddharth, how is this additional data provided, and how many records of data is it, and how does it correlate to the other data you are ingesting? If the data is very small you can use cut-and-paste to ingest small amounts of data directly on the console. Otherwise it would likely need to be ingested in one of the available file formats. But ultimately it would need to be ingested into a datasource (table) or lookup (key/value map).

Let's say a user has a file called Health.csv which contains data of patients for the year 2019 from a specific hospital. The "Description" would be a string that would be something like "Data for Patients from Some Example Hospital", and the "Year" would be "2019". I also want this data to be removed if I remove the related data sources from Druid.

Okay so you are asking for metadata for the datasources you are creating. I don't know of anything other than creating a separate datasource to hold this metadata. Two ways I can think of offhand: • If you create a single "metadata" datasource for the entire cluster, this would have one record of metadata per datasource, and if you wanted to update or delete any records you would have to run a quick reingestion job on the entire datasource to make the change. This would run quickly, could be driven via API if you want ... and could be done via SQL using the MSQ API. • You could also create a separate datasource corresponding to each datasource to hold the metadata for that one datasouce ... this would have only only record in it, maybe you name it in a convenient way (e.g. "<datasource_name>_meta") which makes it easy to delete when you delete the corresponding datasource. Would either of those work for you?