Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/12191#issuecomment-211212703
@bomeng sorry for not getting back to you sooner. Is sorting the list only
for asthetics and ease of searching? It seems like it is not really worth
effort if it is, what do you think?
It might have a little merit in terms of performance to group all
`nonReserved` keywords together. The parser has to check if a Token is on the
nonReserved list and it does this by switch statements. Having a complete range
of nonReserved tokens might allow a JIT/Compiler to optimize this.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
