cj-zhukov commented on PR #20421:
URL: https://github.com/apache/datafusion/pull/20421#issuecomment-3988809524

   > > Given that, I’m wondering if it would make sense to keep this PR focused 
and open a separate PR dedicated specifically to supporting both syntaxes.
   > 
   > Probably
   > 
   > I am just worried about disallowing syntax that was previously allowed as 
I worry it will cause downstream issues (we have hit stuff like this in the 
past at InfluxData)
   > 
   > From a customers perspective they are like "my query use to work but no 
longer does"
   > 
   > Unless we have some sort of more compelling story (like "it was getting 
the wrong answer and now you get an error which is better") it is hard to 
justify such changes
   
   Thanks for clarifying - that makes sense.
   I agree that preserving previously supported syntax is important for 
downstream users, especially to avoid unexpected regressions.
   
   I’ll update this PR to continue supporting both syntaxes rather than 
introducing a breaking change. I’ll follow up once I have a clean solution in 
place.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to