visch
08/31/2021, 7:58 PMtime=2021-08-31 15:54:32 name=tap-clickup level=WARNING message=Property 'team_id' was present in the 'space' stream but not found in catalog schema. Ignoring.
it looks like the team_id gets added into my space stream because Team is a parent of Space in this case. Is the idea that the tap developed should add team_id to the schema for the data coming from the space object? Seems a bit odd as team_id
isn't in the data that comes from the space api query.
Maybe I'm missing something, thought I'd ask first before throwing in an issueaaronsteers
08/31/2021, 10:06 PMaaronsteers
08/31/2021, 10:08 PMvisch
08/31/2021, 11:17 PMaaronsteers
08/31/2021, 11:42 PMBy default why not add the property to the schema then?Perhaps we should! I'm not sure which approach is better, tbh.
Hmm I understand the debugging want, but I don't like the idea of adding things that are not from the actual source. A convention like sdc_space_id or something like sounds like the best of both worldsCertainly I think there's space to refine and improve - I don't love an infinite/unbound count of
_sdc_
columns but perhaps a single _sdc_partition_context
could hold a complex dict of the parent context, and/or something like _sdc_parent_context
. Would be a much appreciated issue topic and/or office hours topic. 🙂visch
09/01/2021, 12:28 AMvisch
09/01/2021, 12:28 AM