If a data source has columns which are variable in...
# singer-tap-development
h
If a data source has columns which are variable in nature, specific to the caller of the API (the account specifically), what is the best way to handle this in Stream implementation? Some options I've thought of: • Make the user specify all account specific columns as part of the configuration • Dynamically produce the schema based on the response from the data source