[ 
https://issues.apache.org/jira/browse/HIVE-16197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969725#comment-15969725
 ] 

Sushanth Sowmyan commented on HIVE-16197:
-----------------------------------------

Thanks for the update with the changes, [~sankarh], I'm +1 on .04.patch, and 
will go ahead and commit it. The 2 unit tests that failed above are unrelated 
so I'm going to ignore those failures.

That said, I do have 2 comments/questions:

a) Is there a reason you changed the "replace" field from Boolean to String in 
JSONInsertMessage.java ? The change is effectively equivalent and I don't mind, 
but is there an issue with the json parsing that you noticed that prompted you 
to make that change from .03.patch to .04.patch?
b) In general, I think that when changing thrift structures, it has been 
standard practice to always add new fields at the "end", rather than the 
beginning - i.e., if a struct already has numbered elements for 1&2, then a new 
field should always be added as 3, rather than adding it as 1, and bumping the 
prior 1&2 to 2&3. I had to check to see whether doing so breaks backward 
compatibility (i.e. is ordering of field numbers important?) and from reading 
docs, I can't find anything that indicates that that is a problem, and so the 
patch is fine as-is. If there were reason to regenerate this patch, I would 
suggest changing it, but at this point, I think it's fine to leave it as-is.

> Incremental insert into a partitioned table doesn't get replicated.
> -------------------------------------------------------------------
>
>                 Key: HIVE-16197
>                 URL: https://issues.apache.org/jira/browse/HIVE-16197
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR
>         Attachments: HIVE-16197.01.patch, HIVE-16197.02.patch, 
> HIVE-16197.03.patch, HIVE-16197.04.patch
>
>
> Insert to a partitioned table doesn't replicate properly in case of 
> incremental dump/load. Few key points to be noted.
> 1. If insert command itself created the new partition, then the inserted row 
> is replicated. But the subsequent inserts into the same table doesn't get 
> replicated.
> 2. If the partition is created using ALTER TABLE command, then none of the 
> inserted rows to this partition is getting replicated. However, the partition 
> metadata is getting replicated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to