-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kafka-influxdb-sink cannot handle Avro type array anymore #737
Comments
Hi @afausti , This code was not touched (even if you look at the history). Line 78 in 8c3239b
So I am not sure when the influxdb sink ever supported inserting an array. I see indeed you added the point handling at higher level when array support were added. So it's best to inject the handling lower in the code i shared. We will add it back |
@stheppi nice, thank you, yes the solution in that PR was to extract the elements of the array and write them as new fields in InfluxDB. It used to work like this:
|
Please consider adding a test to ensure that the connector can handle arrays with |
@stheppi just checking if there plans on adding this feature back. Thank you! |
@afausti yes, we will be working to add it back |
I can confirm that the new array handling implementation works fine for me. I've built This issue can be closed. |
@afausti thanks! |
Issue Guidelines
What version of the Stream Reactor are you reporting this issue for?
2.1.3
Are you running the correct version of Kafka/Confluent for the Stream reactor release?
Yes, with Confluent Kafka 5.5.2
Have you read the docs?
Yes
What is the expected behaviour?
I would expect kafka-influxdb-sink 2.1.3 to support Avro records of type array (see PR #522) In fact I contributed that PR in the past, but I didn't include a test for it :(
I can try to fix this with some guidance.
What was observed?
What is your Connect cluster configuration (connect-avro-distributed.properties)?
What is your connector properties configuration (my-connector.properties)?
Please provide full log files (redact and sensitive information)
The text was updated successfully, but these errors were encountered: