[GitHub] incubator-carbondata pull request #387: [CARBONDATA-490] [SPARK2] Unify all ...

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-carbondata pull request #387: [CARBONDATA-490] [SPARK2] Unify all ...

qiuchenjian-2
GitHub user jackylk opened a pull request:

    https://github.com/apache/incubator-carbondata/pull/387

    [CARBONDATA-490] [SPARK2] Unify all RDD in carbon-spark and carbon-spark2 modules

    Currently there are duplicate RDD in carbon-spark and carbon-spark2 modules. This PR unify them and move them to carbon-spark-common module.


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

    $ git pull https://github.com/jackylk/incubator-carbondata rdd

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

    https://github.com/apache/incubator-carbondata/pull/387.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 #387
   
----
commit 4c8513e57e5e622d68b29f10b2181ac796659ee4
Author: jackylk <[hidden email]>
Date:   2016-12-02T15:54:49Z

    modify all RDD

commit ee18fd20bf318141b0295aef02c98fc901aea05b
Author: jackylk <[hidden email]>
Date:   2016-12-03T05:48:29Z

    rebase

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-carbondata issue #387: [CARBONDATA-490] [SPARK2] Unify all RDD in ...

qiuchenjian-2
Github user jackylk commented on the issue:

    https://github.com/apache/incubator-carbondata/pull/387
 
    CI:
    http://136.243.101.176:8080/job/ApacheCarbonManualPRBuilder/736/


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-carbondata issue #387: [CARBONDATA-490] [SPARK2] Unify all RDD in ...

qiuchenjian-2
In reply to this post by qiuchenjian-2
Github user jackylk commented on the issue:

    https://github.com/apache/incubator-carbondata/pull/387
 
    CI passed
    http://136.243.101.176:8080/job/ApacheCarbonManualPRBuilder/745/


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-carbondata issue #387: [CARBONDATA-490] [SPARK2] Unify all RDD in ...

qiuchenjian-2
In reply to this post by qiuchenjian-2
Github user chenliang613 commented on the issue:

    https://github.com/apache/incubator-carbondata/pull/387
 
    LGTM


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-carbondata pull request #387: [CARBONDATA-490] [SPARK2] Unify all ...

qiuchenjian-2
In reply to this post by qiuchenjian-2
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-carbondata/pull/387


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---