[GitHub] [carbondata] study-day commented on issue #4173: DELETE FROM TABLE default.test_table WHERE SEGMENT.ID IN reported an error in benline

study-day commented on issue #4173: URL: https://github.com/apache/carbondata/issues/4173#issuecomment-886418870 thanks thanks thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specifi

[GitHub] [carbondata] study-day closed issue #4173: DELETE FROM TABLE default.test_table WHERE SEGMENT.ID IN reported an error in benline

study-day closed issue #4173: URL: https://github.com/apache/carbondata/issues/4173 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubsc

[GitHub] [carbondata] nihal0107 commented on issue #4173: DELETE FROM TABLE default.test_table WHERE SEGMENT.ID IN reported an error in benline

nihal0107 commented on issue #4173: URL: https://github.com/apache/carbondata/issues/4173#issuecomment-886379874 There is some ten valid segment status. You can refer to the file `SegmentStatus.java`. Once we trigger the load and if the load will be success then segment status will be

[GitHub] [carbondata] study-day commented on issue #4182: FusionInsightHD 6518 spark2.3.2 carbon-2.0.0 skewedJoin adaptive execution no use.

study-day commented on issue #4182: URL: https://github.com/apache/carbondata/issues/4182#issuecomment-886306886 hi ,kongxianghe, We have also found a similar problem. If two tables are join, it will be very time-consuming if there is no de-duplication. And spark only uses a few executors.