Connector Improvement: Pylon (lite) Connector Improvement
AnsweredWe are seeing some fields in the issue table not being imported correctly into our data warehouse. The Fivetran Lite Connector maps each custom field to a custom_<field_name> column by reading the .value key as a scalar. That works for every other field because .value is a string. For time_in_status, .value is {"new": "3600", "waiting_on_customer": "7200", "closed": "1800", ...} - an object - so the connector either can't represent it in the standard column pattern or silently drops it.
Furthermore we are interested in ingesting the sub endpoint
-
Official comment
Hi Bastian Gerstner,
Thank you for taking the time to share the detailed context around the
time_in_statusfield and the/issues/{id}/threadsendpoint. We truly appreciate the clarity you’ve provided.For custom fields, the Lite connector typically reads the
.valuekey as a scalar. In cases where the structure differs or we encounter non scalar formats, we aim to retain the data in its original structure within the same field wherever possible. That said, we understand how this specific object format can create inconsistencies and we will review it more closely.I have added both the structured handling of
time_in_statusand support for the/threadsendpoint to our backlog for review and prioritization. These will be evaluated based on overall demand and technical considerations.While I’m unable to share a specific ETA at this time, we will keep you informed of any updates. If you have any further questions or would like to discuss this in more detail, please feel free to reach out to our Support team.
Thank you again for your engagement and thoughtful feedback.
Best regards,
Syead Mujtaba Imam Rizwi
Please sign in to leave a comment.
Comments
1 comment