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

Hadoop QA commented on PHOENIX-5232:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12965656/PHOENIX-5232-addendum.patch
  against master branch at commit 6ca7ff61ca9d8d89343fb331aed25afe174c8ca5.
  ATTACHMENT ID: 12965656

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2505//console

This message is automatically generated.

> PhoenixDataWriter in Phoenix-Spark connector does not commit when mutation 
> batch size is reached
> ------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5232
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5232
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.15.0
>            Reporter: Chinmay Kulkarni
>            Assignee: Chinmay Kulkarni
>            Priority: Major
>         Attachments: PHOENIX-5232-addendum.patch, PHOENIX-5232.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We do not keep track of the number of records written and do not get the 
> batch size. We should ideally commit mutations each time the batch size has 
> been reached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to