GitHub user jmahonin opened a pull request:

    https://github.com/apache/phoenix/pull/59

    PHOENIX-1071 Add phoenix-spark for Spark integration

    This adds a new module which can be used to load and save Phoenix tables 
through the Spark 1.3.0+ DataFrame and RDD APIs.
    
    It's based originally on https://github.com/simplymeasured/phoenix-spark 
with significant modifications to bump the Phoenix and Spark dependencies, and 
also adds the write() implementation to PhoenixRecordWritable
    
    Usage examples and further documentation can be found in README.md. Even 
more usage examples can be found in PhoenixRDDTest.
    
    I've attempted to adhere to the ASF guidelines, adding the appropriate 
headers and attribution in NOTICE. I'm not entirely clear on the guidelines for 
moving Copyright notices from original source files, but I've contacted the 
Simply Measured folks for approval to do so, if necessary.
    
    I also have branch which merges on the 4.3 branch I've been using 
internally, which I can submit as well. The only merge conflicts are the NOTICE 
file, the modules listed in /pom.xml, and the parent POM version in 
/phoenix-spark/pom.xml
    
    Please let me know if there's anything more I can provide in terms of 
explanation, documentation, testing, etc.

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

    $ git pull https://github.com/FileTrek/phoenix phoenix-spark-master

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

    https://github.com/apache/phoenix/pull/59.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #59
    
----
commit 59852d1ba413b9505275db6e098b4947cf79bf3f
Author: Josh Mahonin <[email protected]>
Date:   2015-03-25T19:40:10Z

    PHOENIX-1071 Add phoenix-spark for Spark integration

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to