where can i find your roadmap

You can find Airbyte's public roadmap on GitHub: [Airbyte Roadmap] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai i cant see it. tell me whats on it

I'm sorry, but the knowledge sources do not contain enough information to give you a full breakdown of the current roadmap contents. However, based on what is available, here are some roadmap items that have been mentioned: Connector Builder improvements (open roadmap item): • Concurrency levels and API budgets • Better and cleaner error reporting [Connector Builder Roadmap] Connector migration to low-code format (closed/completed): • HubSpot, Google Analytics, Google Search Console, Jira, LinkedIn Ads, and Airtable have already been migrated. [Low-code Migration Roadmap] For the most up-to-date and complete roadmap, I'd recommend: • Visiting the Airbyte GitHub Roadmap directly • Joining the Airbyte Community Slack to ask the team directly [Airbyte README] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai how do i parse a jsonl in a custom integration builder

Parsing JSONL in the Connector Builder To parse a JSON Lines (JSONL) response in Airbyte's Connector Builder, you need to set the HTTP Response Format to JSON Lines. What is JSONL? JSONL is a text format where each line is a separate JSON object, for example:

{"name": "John", "age": 30, "city": "New York"}
{"name": "Alice", "age": 25, "city": "Los Angeles"}
{"name": "Bob", "age": 50, "city": "Las Vegas"}

How to configure it In the Connector Builder UI, set the HTTP Response Format to JSON Lines. This tells the connector to decode the response by splitting it on newlines (

\n

) and parsing each line as a separate JSON object. [Record Parsing docs] In YAML (config-based) If you are working directly in the YAML manifest, use the

JsonlDecoder

component:

decoder:
  type: JsonlDecoder

This will handle responses consisting of JSON objects separated by newlines in JSONL format. [YAML Reference] Important note on Content-Type There is no standardized

Content-Type

header for JSONL responses. APIs commonly return

text/html

or

text/plain

for JSONL content, so you should consult the API's documentation to confirm the expected content type. [Record Parsing docs] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.