-
Notifications
You must be signed in to change notification settings - Fork 175
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
Lookup not working with multi-partitioned topics #186
Comments
I haven't tried running your code but it looks good to me. As you initially thought, lookup tables can have any number of partitions. How was your |
Many Thanks for your reply. I created t_lookup using the Kafka-topics console client. How/where can I overwrite the golang hash function? Thanks |
To set the hasher you have to pass the You can create the processor like this:
Also take a look in the tips page, you may find something useful: https://github.com/lovoo/goka/wiki/Tips Let me know if that was helpful. |
Thanks very much. The MurmurHasher works like a charm with multiple partitions :) Thanks again |
Hello community,
I am developing a streaming app and my case is the following:
<t_lookup>
, which will be used for lookups, log compaction enabled<goka.Lookup(lookupTable, new(codec.String))>
<input_stream>
and my whole Graph declaration is:<g := goka.DefineGroup(lookupGroup, goka.Input(lookupSourceTopic, new(codec.String), perfromJoin), goka.Lookup(lookupTable, new(codec.String)), )>
<ctx.Lookup(lookupTable, ctx.Key())>
, I dont find any match although there are matches in<t_lookup>
.<t_lookup>
with only one partition, matches are found.So my question is: Does a topic used for lookups need to have just one partition or am I missing something here.
I have attached my whole sourcecode.
Many Thanks in advance
lookup.txt
The text was updated successfully, but these errors were encountered: