You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the payload is the only part of a kafka record that’s parsed from what I can tell. It would be nice to be able to extract information from headers and keys as well.
The text was updated successfully, but these errors were encountered:
This is a great suggestion. We don't currently have a plan to add such a feature, but this would be a great contribution.
Some initial thoughts to contribute:
To preserve API compatibility, we could add a new (optional / opt-in) flag to a kafka ingest configuration like includeMeta: Boolean = false (indicating it defaults to false if unspecified in the JSON payload)
When includeMeta is true, the $that value passed to the ingest query could take a different shape -- for example
{
kafkaMeta: ...,
data: ... (i.e., $that if includeMeta were false)
}
Negotiating this type change between the "ingest source layer" (i.e., "kafka") and the "ingest format layer" (e.g., CypherJson, CypherProtobuf) could be a bit tricky -- the format needs to be aware since that layer goes bytes => intermediate records but the ingest source layer also needs to be aware since that layer goes connection to kafka => record bytes. Not sure how to resolve that.
Currently, the payload is the only part of a kafka record that’s parsed from what I can tell. It would be nice to be able to extract information from headers and keys as well.
The text was updated successfully, but these errors were encountered: