Github user CarbonDataQA commented on the issue:
https://github.com/apache/carbondata/pull/1149
Build Failed with Spark 2.1.0, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/3141/
---
If your project is set up for it, you can reply to this email and have
Github user CarbonDataQA commented on the issue:
https://github.com/apache/carbondata/pull/1149
Build Failed with Spark 1.6, Please check CI
http://144.76.159.231:8080/job/ApacheCarbonPRBuilder/549/
---
If your project is set up for it, you can reply to this email and have your
Github user gvramana commented on the issue:
https://github.com/apache/carbondata/pull/1149
@ravipesala Previously schema refresh is using store level timestamp file
and then table schema file modification timestamp. How now refresh is detected?
---
If your project is set up for
Github user jackylk commented on the issue:
https://github.com/apache/carbondata/pull/1149
LGTM
Test case need to be solved in another PR
---
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
Github user CarbonDataQA commented on the issue:
https://github.com/apache/carbondata/pull/1149
Build Failed with Spark 1.6, Please check CI
http://144.76.159.231:8080/job/ApacheCarbonPRBuilder/431/
---
If your project is set up for it, you can reply to this email and have your
Github user CarbonDataQA commented on the issue:
https://github.com/apache/carbondata/pull/1149
Build Failed with Spark 2.1.0, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/3019/
---
If your project is set up for it, you can reply to this email and have
Github user CarbonDataQA commented on the issue:
https://github.com/apache/carbondata/pull/1149
Build Success with Spark 2.1.0, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/2998/
---
If your project is set up for it, you can reply to this email and have