-
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-1881] Insert overwrite value for pre-aggregate load was incorrect #1639
Conversation
Build Failed with Spark 2.2.0, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/631/ |
Retest this please |
Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1860/ |
Build Success with Spark 2.2.0, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/633/ |
Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1862/ |
SDV Build Fail , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/2205/ |
LGTM |
retest sdv please |
SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/2237/ |
…ncorrect While loading the value for insert overwrite was set to false. Consider the value of insert overwrite set for maintable for pre-aggregate table loading. This closes apache#1639
…ncorrect While loading the value for insert overwrite was set to false. Consider the value of insert overwrite set for maintable for pre-aggregate table loading. This closes apache#1639
…ncorrect While loading the value for insert overwrite was set to false. Consider the value of insert overwrite set for maintable for pre-aggregate table loading. This closes apache#1639
Analysis: while loading the value for insert overwrite was set to false.
Solution: Consider the value of insert overwrite set for maintable for pre-aggregate table loading.
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.