-
Notifications
You must be signed in to change notification settings - Fork 703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CARBONDATA-1801] Remove unnecessary mdk computation code #1636
Conversation
Can one of the admins verify this patch? |
2 similar comments
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
add to whitelist |
Build Failed with Spark 2.2.0, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/699/ |
Build Failed with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1928/ |
retest this please |
@kevinjmh there are some findbugs issues, please check. |
Build Failed with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1930/ |
Build Failed with Spark 2.2.0, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/702/ |
SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/2261/ |
Build Success with Spark 2.2.0, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/715/ |
Build Success with Spark 2.2.0, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/719/ |
Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1947/ |
SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/2270/ |
SDV Build Fail , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/2273/ |
@kevinjmh this pr , looks you introduced many other commit record? |
@kevinjmh suggest you first close this pr, then raise a new one. |
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:
[No] Any interfaces changed?
[No ] Any backward compatibility impacted?
[ No] Document update required?
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.