Member since
06-26-2015
505
Posts
127
Kudos Received
114
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
642 | 09-20-2022 03:33 PM | |
2055 | 09-19-2022 04:47 PM | |
1211 | 09-11-2022 05:01 PM | |
1303 | 09-06-2022 02:23 PM | |
1879 | 09-06-2022 04:30 AM |
09-05-2022
03:09 PM
@samrathal , What about this: [
{
"operation": "default",
"spec": {
"currenttime": "${now():toNumber()}",
"timeOneMinu": "${now():toNumber():minus(60)}"
}
}
]
... View more
09-05-2022
05:37 AM
@samrathal , Doesn't your JOLT spec solve your own problem? Cheers, André
... View more
09-04-2022
10:21 PM
@syntax_ , It seems to me that your source Kafka is a Confluent Kafka cluster and the producer uses schema registry to source the schema from it. In this case, the KafkaAvroSerializer prepends 5 bytes to every message produced to indicate the id of the schema that was used (in you case, schema id 34). If you try to read this message as a pure Avro payload the deserialization will fail because those 5 bytes are not part of the Avro payload. So, the best way to handle this in NiFi is to also use Schema Registry to deserialize Avro messages. With this, NiFi will get the schema ID from the message 5-byte prefix, use that ID to retrieve the correct schema from Schema Registry and then correctly deserialize the Avro payload. Considering that my guess is correct and you're using a Confluent Schema Registry, you should create a new ConfluentSchemaRegistry controller service and configure it with the details of your Schema Registry. Once this is done, edit the configuration of the Avro Reader controller service and set the following: After you do this, your flow should be able to correctly process the messages that you're reading from Kafka. I read the binary message that you send me with NiFi and loaded the schema in my local schema registry service (making sure it got assigned the right ID 34), and I was able to successfully convert the message from Avro to JSON using a ConvertRecord processor: Cheers, André
... View more
09-04-2022
06:15 PM
@Uday483 , The error above happens if you don't specify the domain during authentication, right? If you do specify the domain, does it work? André
... View more
09-04-2022
05:32 PM
@hebamahmoud , Did you try enabling the dependency between Kudu and Impala, as per my post above? Cheers, André
... View more
09-04-2022
05:29 PM
@syntax_ , Please try running this command: xxd message.avro Then you can copy and paste the output here. Cheers, André
... View more
09-02-2022
03:18 AM
Ok. Did you try the ldap configuration I mentioned above? Cheers André
... View more
09-02-2022
03:16 AM
Can you please send me that file in a private message. Copy and paste won't work 🙂 Cheers, André
... View more
09-01-2022
10:25 PM
@hebamahmoud , Try enabling the Kudu Service as a dependency for the Impala service, as shown below. When you do that Impala will use the selected Kudu service as the default service whenever you use a Kudu table that does not explicitly sets the Kudu masters. If you don't set the property above you can still use Kudu from Impala but when you create the table you have to specify the Kudu masters through the TBLPROPERTIES clause. Cheers, André
... View more