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

ASF GitHub Bot commented on PHOENIX-40:
---------------------------------------

GitHub user JamesRTaylor opened a pull request:

    https://github.com/apache/incubator-phoenix/pull/3

    PHOENIX-40: Add support for batching

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/incubator-phoenix master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-phoenix/pull/3.patch

----
commit d542e73124652672d71efe9cd968f8e6ba09288b
Author: James Taylor <[email protected]>
Date:   2014-02-11T23:34:33Z

    Basic batch update support

commit e75538e66f3393e4d22c3367385b9f23a2dcca6d
Author: James Taylor <[email protected]>
Date:   2014-02-12T01:40:16Z

    Make ExecutableStatement stateless to prevent reparsing for batch updates

commit c33326b34c10f8a66f50ad1b74e5dd5b23cc330e
Author: James Taylor <[email protected]>
Date:   2014-02-12T07:50:16Z

    Cleanup PhoenixStatement by standardizing and removing copy/paste code

commit 26cb1353e3bfc911423cefc59817e19ec940e84f
Author: James Taylor <[email protected]>
Date:   2014-02-12T07:50:49Z

    Merge remote-tracking branch 'upstream/master'

----


> Add support for batching
> ------------------------
>
>                 Key: PHOENIX-40
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-40
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 3.0.0
>
>
> In the case of Phoenix, since it's an embedded driver, there's no real 
> advantage or need for batching. However, Pig relies on JDBC drivers to 
> support batching, so we should do the minimal amount of work such that we can 
> interop.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to