[
https://issues.apache.org/jira/browse/HIVE-23150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077447#comment-17077447
]
David Lavati commented on HIVE-23150:
-------------------------------------
[~belugabehr] TableName currently uses splitting because there are too many
cans of worms that need to be opened/resolved for it's internals to be more
sophisticated. I chose to weed out a lot of String manipulation and organize it
under a class, which then can be globally refactored at least.
Changing 1 single thing that affects a core ql function, can ripple out to
hundreds of test cases, so most approaches seemed to be painful either way.
Similarly to your idea, I wanted to do multiple steps under HIVE-21630, but
recently I haven't had much time to finish HIVE-22585.
As for refactoring, some bothersome hotspots are around replication, material
views, security.
Nonetheless it's good to see that more of us are looking at this group of
issues :)
> Create an Object Identifier Parser for All Components to Use
> ------------------------------------------------------------
>
> Key: HIVE-23150
> URL: https://issues.apache.org/jira/browse/HIVE-23150
> Project: Hive
> Issue Type: Sub-task
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Major
> Attachments: HIVE-23150.1.patch
>
>
> Create a parser for parsing (and validating) MySQL/MariaDB style object
> identifiers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
