Github user watermen commented on the issue:
https://github.com/apache/incubator-carbondata/pull/659
@jackylk If I want to reuse `SegmentProperties` and only check the
parameters `columnsInTable` and `columnCardinality`, which case I will
missing(wrong case)? Because compare
Github user jackylk commented on the issue:
https://github.com/apache/incubator-carbondata/pull/659
I checked recently merged PR641 for restructuring, it seems that this is
still used for maintaining metadata for each Segment, so it canât be changed
to TableProperties.
One
Github user CarbonDataQA commented on the issue:
https://github.com/apache/incubator-carbondata/pull/659
Build Failed with Spark 1.6.2, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/1200/
---
If your project is set up for it, you can reply to this email and
Github user jackylk commented on the issue:
https://github.com/apache/incubator-carbondata/pull/659
Earlier, this was used for handling restructure information. Now it is
handled in another way, so yes we should change it to reduce the number of
objects
---
If your project is set
Github user CarbonDataQA commented on the issue:
https://github.com/apache/incubator-carbondata/pull/659
Build Failed with Spark 1.6.2, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/1186/
---
If your project is set up for it, you can reply to this email and
Github user CarbonDataQA commented on the issue:
https://github.com/apache/incubator-carbondata/pull/659
Build Failed with Spark 1.6.2, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/1168/
---
If your project is set up for it, you can reply to this email and
