[
https://issues.apache.org/jira/browse/HIVE-18052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416589#comment-16416589
]
Sergey Shelukhin commented on HIVE-18052:
-----------------------------------------
Attached the patch.
I was assuming during initial process above that this is test only patch but
there are actually some fixes and changes there. Some of these got lost because
of conflicts with master in my upload.
[~steveyeom2017] we urgently need to get these fixes that already exist on
master... maintaining them in some floating patches is not sustainable.
Also there were many out files conflicts that I've ignored (it's easier to look
at files again than to resolve out file conflicts).
I think at this point we should
1) Get existing fixes in.
2) Do a quick check on failures from this run and identify basic blocking
issues and missing functionality.
3) Make new fixes, repeat from (1).
Throughout this process we can determine when this is shippable, ie when
remaining gaps are small/trivial/obscure and we can just disable them and fix
them later via the same process.
Otherwise attempt to make one epic fix patch will take too long.
[~steveyeom2017] also do you know if the patch/some other jira has full load
overwrite implementation? I'm not sure about the state of that.
> Run p-tests on mm tables
> ------------------------
>
> Key: HIVE-18052
> URL: https://issues.apache.org/jira/browse/HIVE-18052
> Project: Hive
> Issue Type: Task
> Reporter: Steve Yeom
> Assignee: Steve Yeom
> Priority: Major
> Attachments: HIVE-18052.1.patch, HIVE-18052.10.patch,
> HIVE-18052.11.patch, HIVE-18052.12.patch, HIVE-18052.13.patch,
> HIVE-18052.14.patch, HIVE-18052.15.patch, HIVE-18052.16.patch,
> HIVE-18052.17.patch, HIVE-18052.18.patch, HIVE-18052.2.patch,
> HIVE-18052.3.patch, HIVE-18052.4.patch, HIVE-18052.5.patch,
> HIVE-18052.6.patch, HIVE-18052.7.patch, HIVE-18052.8.patch, HIVE-18052.9.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
