-
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-1713] Fixed Aggregate query on main table fails after creating pre-aggregate table #1501
Conversation
Build Failed with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1148/ |
541113a
to
db22e1d
Compare
SDV Build Fail , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/1734/ |
Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1157/ |
retest sdv please |
SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/1744/ |
Table name and column name are case sensitive, right? |
Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/1406/ |
SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/1851/ |
@jackylk tablename, dbname and column names are case insensitive in carbon |
LGTM |
…ating pre-aggregate table Problem: when select query columns are in upper case pre aggregate table selection is failing Solution:: Need to convert column name to lower case as table columns are in lower case This closes apache#1501
…ating pre-aggregate table Problem: when select query columns are in upper case pre aggregate table selection is failing Solution:: Need to convert column name to lower case as table columns are in lower case This closes apache#1501
Problem: when select query columns are in upper case pre aggregate table selection is failing
Solution:: Need to convert column name to lower case as table columns are in lower case
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:
Any interfaces changed?
Any backward compatibility impacted?
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.