Atul Mohan

It's possible that Druid ignored the unparseable rows. Please check the task reports corresponding to the ingestion task to see if there were unparseable records encountered. If you require tasks...

@mounikanakkala We have similar use cases internally for which we've been working on a configurable option to periodically remove older lookup-related audit entries. I'll raise the PR once it is...

Thanks for the contribution @churromorales ! Looking forward to the followup PRs to handle the outstanding items identified from this PR.

Thanks for your insights @gianm From the [Calcite debug logs](https://gist.github.com/a2l007/d84a51a4ced915e57a3adf9bda40a0fa), I see the following activity within the `HepPlanner`: ``` org.apache.calcite.plan.RelOptPlanner - call#0: Apply rule [ReduceExpressionsRule(Project)] to [rel#38:LogicalProject.NONE.[](input=HepRelVertex#37,EXPR$0=$2,countryName=$1)] org.apache.calcite.plan.RelOptPlanner - call#0:...

@mkuthan The first step would be to add an ability to add store settings into a database. With the support of a database, the state of the reports can be...

@mkuthan Thank you for your response. I've re-evaluated the priorities and following are my thoughts: - I completely agree that dashboards without security is a bad idea and we have...

@adrianmroz I have not used 1.15 yet but the ability to construct more complex measures sounds interesting. But how are the new complex measures persisted? From your comment, I assume...

> we find it as a nice tradeoff for exploratory data analysis. Could you please explain why would you need a tradeoff for exploratory data analysis? It looks like the...

> For sure we can't work on such feature and we need to keep turnilo compatible. Separate app could be a better start and maybe we can integrate it later?...

Thanks for the comment. I'll make sure to post updates once we have a working model ready.