[GitHub] carbondata pull request #2162: [CARBONDATA-2337] Fix duplicately acquiring '...

2018-04-13 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/carbondata/pull/2162


---


[GitHub] carbondata pull request #2162: [CARBONDATA-2337] Fix duplicately acquiring '...

2018-04-11 Thread zzcclp
GitHub user zzcclp opened a pull request:

https://github.com/apache/carbondata/pull/2162

[CARBONDATA-2337] Fix duplicately acquiring 'streaming.lock' error when 
integrating with spark-streaming.


After merged [PR2135](https://github.com/apache/carbondata/pull/2135), it 
will acquire 'streaming.lock' duplicately when integrating with spark-streaming.

Be sure to do all of the following checklist to help us incorporate 
your contribution quickly and easily:

 - [ ] Any interfaces changed?  No
 
 - [ ] Any backward compatibility impacted?   No
 
 - [ ] Document update required?   No

 - [ ] Testing done
Please provide details on 
- Whether new unit test cases have been added or why no new tests 
are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance 
test report.
- Any additional information to help reviewers in testing this 
change.
   
 - [ ] For large changes, please consider breaking it into sub-tasks under 
an umbrella JIRA. 



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

$ git pull https://github.com/zzcclp/carbondata CARBONDATA-2337

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

https://github.com/apache/carbondata/pull/2162.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 #2162


commit c491e4e927840016f0279e2c82959c9d2e2d8b19
Author: Zhang Zhichao <441586683@...>
Date:   2018-04-12T04:24:45Z

[CARBONDATA-2337] Fix duplicately acquiring 'streaming.lock' error when 
integrating with spark-streaming.

After merged [PR2135|https://github.com/apache/carbondata/pull/2135], it 
will acquire 'streaming.lock' duplicately when integrating with spark-streaming.




---