You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/01/11 05:44:41 UTC
[GitHub] glasser commented on issue #6715: [Proposal] time granularity based
materialized view
glasser commented on issue #6715: [Proposal] time granularity based materialized view
URL: https://github.com/apache/incubator-druid/issues/6715#issuecomment-453385522
We'd love something like this in order to keep a longer range of data at lower granularity in a second copy of our data sources. Does anyone have any workarounds for implementing something like that today? I guess we can use batch ingestion with the ingestSegment firehose to do this, but we still have to create something that periodically starts batch ingestion.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org