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 2022/12/02 18:24:39 UTC

[GitHub] [druid] sascha-coenen opened a new issue, #6023: Full ISO 8601 compatibility in query intervals

sascha-coenen opened a new issue, #6023:
URL: https://github.com/apache/druid/issues/6023

   The current Druid documentation states in several places that queries have a mandatory "intervals" or "interval" attribute which can contain ISO-8601 compatible intervals.
   
   For instance the documentation on the groupby query (http://druid.io/docs/latest/querying/groupbyquery.html)
   states: "intervals : A JSON Object representing ISO-8601 Intervals. This defines the time ranges to run the query over"
   
   According to the following wikipedia source (https://en.wikipedia.org/wiki/ISO_8601#Time_intervals), there are four valid forms of ISO-8601 intervals:
    
   ```
    <start>/<end>
    <start>/<duration>
    <duration>/<end>
    <duration>
   
   ``` 
   
   It seems that Druid only supports the first three variants. When specifying a duration only, e.g. "P2D", then  Druid returns an exception saying that the "/" character is required within each interval. 
   
   I believe that supporting the last interval format which is a duration relative to the current time (or latest data present in Druid) would be a very useful addition. Most queries involve relative dateranges. If forcing people to use absolute dates, every query needs to be templated such that the timeintervals gets computed by some external logic and then inserted into the query. If the relative duration format was supported, many queries could work without the need of templated injections of external metadata.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] Full ISO 8601 compatibility in query intervals (druid)

Posted by "saketbairoliya2 (via GitHub)" <gi...@apache.org>.
saketbairoliya2 commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-1635335896

   Thanks @abhishekagarwal87 for the response. Have few questions: 
   1. Do SQL based queries have better coverage in terms of features (in-build) functions accessibility? Why do we've a difference in support across native and SQL based queries? 
   2. We're using an alert engine as a client - where it is not practical to pass relative time when submitting the alert rule. 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] Full ISO 8601 compatibility in query intervals (druid)

Posted by "abhishekagarwal87 (via GitHub)" <gi...@apache.org>.
abhishekagarwal87 commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-1635323555

   There are no plans to pick this up since you can do it through SQL. The best way to workaround is to modify the client application so they can resolve the relative duration on their own end and send Druid the absolute duration. Supporting druid sql queries might be too much work in Metabase but maybe resolving a relative duration to an absolute interval is not? I can't say for sure but that direction is worth exploring. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] Full ISO 8601 compatibility in query intervals (druid)

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-2118517943

   This issue has been closed due to lack of activity. If you think that
   is incorrect, or the issue requires additional review, you can revive the issue at
   any time.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] Full ISO 8601 compatibility in query intervals (druid)

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #6023: Full ISO 8601 compatibility in query intervals
URL: https://github.com/apache/druid/issues/6023


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] stale[bot] commented on issue #6023: Full ISO 8601 compatibility in query intervals

Posted by GitBox <gi...@apache.org>.
stale[bot] commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-1335650595

   This issue is no longer marked as stale.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] stale[bot] commented on issue #6023: Full ISO 8601 compatibility in query intervals

Posted by GitBox <gi...@apache.org>.
stale[bot] commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-1335650594

   This issue is no longer marked as stale.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] Full ISO 8601 compatibility in query intervals (druid)

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-2067415988

   This issue has been marked as stale due to 280 days of inactivity.
   It will be closed in 4 weeks if no further activity occurs. If this issue is still
   relevant, please simply write any comment. Even if closed, you can still revive the
   issue at any time or discuss it on the dev@druid.apache.org list.
   Thank you for your contributions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] vogievetsky commented on issue #6023: Full ISO 8601 compatibility in query intervals

Posted by GitBox <gi...@apache.org>.
vogievetsky commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-1335650553

   That makes sense. I will re-open this issue. However this is likely very hard to implement. I am not an expert on this but I think Druid uses the native query interval for the cache key and since a naked duration represents a different interval every second it might mess up the caching strategy.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] snrbrnjna commented on issue #6023: Full ISO 8601 compatibility in query intervals

Posted by GitBox <gi...@apache.org>.
snrbrnjna commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-1327240281

   AFAIK this problem still exists and it should get fixed. @vogievetsky can you perhaps reopen the ticket and give it some attention? 
   
   Using [DSQL](http://druid.io/docs/latest/querying/sql.html) is not an option when visualizing druid data with metabase. 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


Re: [I] Full ISO 8601 compatibility in query intervals (druid)

Posted by "saketbairoliya2 (via GitHub)" <gi...@apache.org>.
saketbairoliya2 commented on issue #6023:
URL: https://github.com/apache/druid/issues/6023#issuecomment-1634386280

   Hi, do we've any update on this feature? Do we've plans to pick this up? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org