You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently in bigquery extractor, one can exclude datasets/tables based on name. But if the tables/dataset list is huge or if there is a need to exclude based on a pattern like tables starting with xx_ or YYYYMMDD_ values, it gets difficult to maintain or modify meteor extractor recipes every time a new format of exclusion comes into the picture.
Add ability to exclude datasets/tables based on labels so that one can attach labels during the table/dataset creation which will be automatically get excluded in meteor extraction.
Describe alternatives you've considered
A regex pattern matching in the name might help for quite a few... but there could be multiple regex patterns that could arise out of this, and it might be cumbersome to maintain / modify in config each time.
The text was updated successfully, but these errors were encountered:
ravisuhag
changed the title
support ability to exclude datasets/tables based on labels in bigquery extractor
Support ability to exclude datasets/tables based on labels in bigquery extractor
Sep 24, 2023
Is your feature request related to a problem? Please describe.
Currently in bigquery extractor, one can exclude datasets/tables based on name. But if the tables/dataset list is huge or if there is a need to exclude based on a pattern like tables starting with
xx_
orYYYYMMDD_
values, it gets difficult to maintain or modify meteor extractor recipes every time a new format of exclusion comes into the picture.Add ability to exclude datasets/tables based on labels so that one can attach labels during the table/dataset creation which will be automatically get excluded in meteor extraction.
Describe alternatives you've considered
A regex pattern matching in the name might help for quite a few... but there could be multiple regex patterns that could arise out of this, and it might be cumbersome to maintain / modify in config each time.
The text was updated successfully, but these errors were encountered: