Alexandru Busuioc
Alexandru Busuioc
@casparjones the Phalcon v4 api (of the common Di services) is slightly changed from v3, so it would not take a huge amount of time to make the phalcon-debugbar compatible...
Thanks for asking. I use only the `attributeOverrides` in configuration file. As described here https://github.com/allegro/turnilo/blob/master/docs/configuration.md#attribute-overrides
Introspection was used when the first configuration file was created. The dimension data type is seen as string, and it is indeed. The issue is when the dimension is used...
Here's what I got.  Since I'm using unions for data sources, and given the dimension types differences at introspection (e.g. in one data source the field is numeric, in...
> We're using `attributeOverrides` when we ingest numeric values as string in order to have [index](https://druid.apache.org/docs/latest/ingestion/schema-design.html#string-vs-numeric-dimensions) on it. It would be great if we could remove `attributeOverrides` section from configuration...
I'm not sure it was mentioned or not, the complex measures (including custom aggregations) can be added actually to config file, and used in data cubes. Add there as much...
Nice to have.
@Gregwar let's have this one merged, please :)
@makasim please run the workflow again.
@makasim please run the workflow.