[jira] [Created] (CARBONDATA-304) Load data failure when set table_blocksize=2048
Gin-zhj created CARBONDATA-304: -- Summary: Load data failure when set table_blocksize=2048 Key: CARBONDATA-304 URL: https://issues.apache.org/jira/browse/CARBONDATA-304 Project: CarbonData Issue Type: Bug Reporter: Gin-zhj Assignee: Gin-zhj First ,create a table with table_blocksize=2048 CREATE TABLE IF NOT EXISTS t3 (ID Int, date Timestamp, country String, name String, phonetype String, serialname String, salary Int) STORED BY 'carbondata' TBLPROPERTIES('table_blocksize'='2048'); Then load data, failure and catch exception: org.apache.carbondata.processing.store.writer.exception.CarbonDataWriterException: Problem while copying file from local store to carbon store -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CARBONDATA-291) Some STATISTIC log still present even though disable STATISTIC
[ https://issues.apache.org/jira/browse/CARBONDATA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gin-zhj resolved CARBONDATA-291. Resolution: Fixed https://github.com/apache/incubator-carbondata/pull/221 > Some STATISTIC log still present even though disable STATISTIC > -- > > Key: CARBONDATA-291 > URL: https://issues.apache.org/jira/browse/CARBONDATA-291 > Project: CarbonData > Issue Type: Bug >Reporter: Gin-zhj >Assignee: Gin-zhj >Priority: Minor > > The following STATISTIC log still present even though disable STATISTIC, > " STATISTIC Time taken for Carbon Optimizer to optimize: 26 " -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CARBONDATA-276) Add trim option
[ https://issues.apache.org/jira/browse/CARBONDATA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565038#comment-15565038 ] ASF GitHub Bot commented on CARBONDATA-276: --- Github user sujith71955 commented on a diff in the pull request: https://github.com/apache/incubator-carbondata/pull/200#discussion_r82758567 --- Diff: processing/src/main/java/org/apache/carbondata/processing/csvreaderstep/UnivocityCsvParser.java --- @@ -102,8 +102,8 @@ public void initialize() throws IOException { parserSettings.setMaxColumns( getMaxColumnsForParsing(csvParserVo.getNumberOfColumns(), csvParserVo.getMaxColumns())); parserSettings.setNullValue(""); -parserSettings.setIgnoreLeadingWhitespaces(false); -parserSettings.setIgnoreTrailingWhitespaces(false); +parserSettings.setIgnoreLeadingWhitespaces(csvParserVo.getTrim()); --- End diff -- Same you need to handle in CarbonFilters.scala also, since while processing filter expressions the spaces are not getting trimmed, so here also you need to take care based on your feature > Add trim option > --- > > Key: CARBONDATA-276 > URL: https://issues.apache.org/jira/browse/CARBONDATA-276 > Project: CarbonData > Issue Type: Bug >Reporter: Lionx >Assignee: Lionx >Priority: Minor > > Fix a bug and add trim option. > Bug: When string is contains LeadingWhiteSpace or TrailingWhiteSpace, query > result is null. This is because the dictionary ignore the LeadingWhiteSpace > and TrailingWhiteSpace and the csvInput dose not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CARBONDATA-239) Failure of one compaction in queue should not affect the others.
[ https://issues.apache.org/jira/browse/CARBONDATA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564600#comment-15564600 ] ASF GitHub Bot commented on CARBONDATA-239: --- Github user sujith71955 commented on a diff in the pull request: https://github.com/apache/incubator-carbondata/pull/224#discussion_r82729006 --- Diff: core/src/main/java/org/apache/carbondata/scan/processor/AbstractDataBlockIterator.java --- @@ -127,11 +133,15 @@ protected boolean updateScanner() { } } - private AbstractScannedResult getNextScannedResult() throws QueryExecutionException { + private AbstractScannedResult getNextScannedResult(QueryStatisticsRecorder recorder, --- End diff -- Why we need to change this getNextScannedResult() method parameters. if required please pass a statistics model, this will make sure that our method parameters wont grow > Failure of one compaction in queue should not affect the others. > > > Key: CARBONDATA-239 > URL: https://issues.apache.org/jira/browse/CARBONDATA-239 > Project: CarbonData > Issue Type: Bug >Reporter: ravikiran >Assignee: ravikiran > Fix For: 0.2.0-incubating > > > Failure of one compaction in queue should not affect the others. > If a compaction is triggered by the user on table1 , and other requests will > go to queue. and if the compaction is failed for table1 then the requests in > queue should continue and at the end the beeline will show the failure > message to the user. > if any compaction gets failed for a table which is other than the user > requested table then the error in the beeline should not appear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)