Re: Data versioning

There are STRINGLAST/LONGLAST or LATEST functions for native or SQL queries, for basic string or number fields. However, if there are cumulative metrics, they can't use these,

Re: [Proposal] - Kafka Input Format for headers, key and payload parsing

I'm not a coder, but wanted to say that I have heard other druid users ask for this functionality, so I think it would be useful. Thank you! On Tue, Sep 7, 2021 at 10:09 AM Lokesh Lingarajan wrote: > Hope everyone had a good long weekend. Any updates/comments ? > > -Lokesh > > > On Mon, Aug 30,

Re: druid can't parse string

Are you using the console, or an ingestion spec? If you use a spec, you might attach it. If you're using the console, and if the strings have commas in them, maybe .tsv would work, and you can create a file with a different delimiter. (In .tsv, you can choose the delimiter; it doesn't have to

Re: A question about a potential bug in Druid Joins

in the code. On Thu, Jun 24, 2021 at 1:27 PM Jason Chen wrote: > Hello, Druid community, > > Ben Krug from Imply points me to this mail list for my question about > Druid Joins. We have a following Druid Join query that may trigger a bug in > Druid: > > quote_type > >

Re: Propose a scheme for Coordinator to pull metadata incrementally

Oh, that's easier than tombstones. flag is_deleted and update timestamp (so it gets pulled again). On Tue, Apr 6, 2021 at 10:48 AM Tijo Thomas wrote: > Abhishek, > Good point. Do we need one more col for storing if it's deleted or not? > > On Tue, Apr 6, 2021 at 4:32 PM Abhishek Agarwal > >

Re: Propose a scheme for Coordinator to pull metadata incrementally

I suppose, if we were going down this path, something like tombstones in Cassandra could be used. But it would increase the complexity significantly. Ie, a new row is inserted with a deletion marker and a timestamp, that indicates that the corresponding row is deleted. Now, when anyone does scan