It is part of the ReadOnlyKeyValueStore interface:
https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyKeyValueStore.java
On Thu, 27 Jul 2017 at 17:17 Shekar Tippur <ctip...@gmail.com> wrote:
> That's cool. This feature is a part of rocksdb object and not ktable?
>
> Sent from my iPhone
>
> > On Jul 27, 2017, at 07:57, Damian Guy <damian....@gmail.com> wrote:
> >
> > Yes they can be strings,
> >
> > so you could do something like:
> > store.range("test_host", "test_hosu");
> >
> > This would return an iterator containing all of the values (inclusive)
> from
> > "test_host" -> "test_hosu".
> >
> >> On Thu, 27 Jul 2017 at 14:48 Shekar Tippur <ctip...@gmail.com> wrote:
> >>
> >> Can you please point me to an example? Can from and to be a string?
> >>
> >> Sent from my iPhone
> >>
> >>> On Jul 27, 2017, at 04:04, Damian Guy <damian....@gmail.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> You can't use a regex, but you could use a range query.
> >>> i.e, keyValueStore.range(from, to)
> >>>
> >>> Thanks,
> >>> Damian
> >>>
> >>>> On Wed, 26 Jul 2017 at 22:34 Shekar Tippur <ctip...@gmail.com> wrote:
> >>>>
> >>>> Hello,
> >>>>
> >>>> I am able to get the kstream to ktable join work. I have some use
> cases
> >>>> where the key is not always a exact match.
> >>>> I was wondering if there is a way to lookup keys based on regex.
> >>>>
> >>>> For example,
> >>>> I have these entries for a ktable:
> >>>> test_host1,{ "source": "test_host", "UL1": "test1_l1" }
> >>>>
> >>>> test_host2,{ "source": "test_host2", "UL1": "test2_l2" }
> >>>>
> >>>> test_host3,{ "source": "test_host3", "UL1": "test3_l3" }
> >>>>
> >>>> blah,{ "source": "blah_host", "UL1": "blah_l3" }
> >>>>
> >>>> and this for a kstream:
> >>>>
> >>>> test_host,{ "source": "test_host", "custom": { "test ": {
> >> "creation_time ":
> >>>> "1234 " } } }
> >>>>
> >>>> In this case, if the exact match does not work, I would like to lookup
> >>>> ktable for all entries that contains "test_host*" in it and have
> >>>> application logic to determine what would be the best fit.
> >>>>
> >>>> Appreciate input.
> >>>>
> >>>> - Shekar
> >>>>
> >>
>
