Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geomesa-users] Kafka Datastore Nifi Component:

Hi Andrew,

Indeed in would make more sense for a Put component to act as a producer, perhaps even still more sense to obscure the isProducer parameter all together and have separate Put and Get components.

 Thanks for the help!

On Sat, Aug 19, 2017 at 2:45 PM, Andrew Hulbert <ahulbert@xxxxxxxx> wrote:

Hi Damon,

Yes, the GeoMesa Nifi component will do two things:

1. Insert metadata into Zookeeper about the topic

2. Create a kafka topic based on the sft name

The Nifi component will use the same params as the Kafka Data Store: http://www.geomesa.org/documentation/user/kafka/usage.html

Note that you need to set the "isProducer" field to "true" in order to write to the kafka datastore from nifi. I opened up a ticket to force this to "true" since it doesn't make sense for it to be false for a "Put" processor.

Let us know if you have any questions!

Andrew


On 08/18/2017 03:27 PM, Stone, Damon wrote:

Hello,

We are trying to use the Geomesa Nifi component to write to a topic in Kafka that doesn't yet exist. 

We would like to understand if the component will create the schema as defined by the sft and converter supplied as parameters, or if the schema needs to be created ahead of time (outside of Nifi) either programmatically or via CLI.

Any insight into this would be a great help. 

-- 

Kind Regards,

Damon



_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users




--

Kind Regards,


Damon P. Stone

Sr GIS Software Developer

Global Data Solutions

Direct: +1 713.329.4856 | Mobile: +1 832.835.4639

dstone@xxxxxxxxxxxxxxx


OII-blue-302c-01.png


11917 FM 529, Houston, TX, USA  |  +1 713.329.4500  |  oceaneering.com



This email is confidential, may be privileged, and should be read or retained only by the intended recipient.

If you have received this email in error, please immediately notify me, delete it from your system and do not retain any copies.

Thank you for your cooperation.


Back to the top