Hello all, I am looking at the source-greenhouse c...
# ask-community-for-troubleshooting
n
Hello all, I am looking at the source-greenhouse connector, and I was wondering if I change json schema in the schemas folder, for example removing primary_email_address from Users.json. Will this not create this column in the destination DB? I see that you can filter out specific streams, but is it possible to filter subfields within the streams (columns in a table)? There might be sensitive data in these fields and I want to filter them out before they land at the destination.
šŸ‘€ 1
āœ… 1
u
Hi @Nikzad Khani, we do not yet offer users to select field they want to ingest, and it's one of our top priority features, especially for the PII use case you mentioned. Here are the workarounds I could suggest: • You can build a custom version of the connector and indeed remove this field from the schema. • You can open a PR on our repo to change the connector and add a configuration flag to discard this field's value.
n
Thanks for the info, if i delete a field from the schema json file, then I should see the change reflected in the fields under the specific table with the same name as the json correct? Additionally, where in the repo is the current table checkbox config handled?
u
If you delete the field from the schema it will be removed from the catalog, you might also have to edit the python code and remove the field in the
parse_response
method of the User stream. All this will require you to fork our repo and rebuild the connector as a custom one for you.
n
Got it, thank you for the information!