Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/15006
@clockfly I also spent some time looking into this :-) I initially tried to
handle this at lexer level and found it difficult distinguish between the
number literals and table names. In particular SCIENTIFIC_DECIMAL looked
troubling like 1234e10. So i tried to solve this at parser rule level where we
have more context to disambiguate between literals and identifiers. I tried the
approach of accepting these literals as table name identifiers and then handle
or reject using the post hook much like how quoted identifiers are handled
today. I have to admit , its a little complex but it handles most of the cases
(based on my current testing).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
