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/12/23 19:57:59 UTC

[GitHub] [druid] glasser commented on issue #6974: sql support for dynamic parameters

glasser commented on issue #6974: sql support for dynamic parameters
URL: https://github.com/apache/druid/pull/6974#issuecomment-568567755
 
 
   Is this still being tracked?
   
   I'm under the impression that folks are encouraged to use SQL as the "default" way of querying Druid these days, with native queries only as an advanced use case, and I'd like to start switching our automated usage over to SQL too when feasible.  But without this support (or a reliable way to escape strings from at least Java code), I'm not comfortable doing so for anything that needs user-controlled substitution...
   
   One note: given that parameters are specified in a list, could it be legal to leave out *all* ordinals and have them default to their 1-based list index if they are all missing?

----------------------------------------------------------------
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.
 
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