You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/15 16:12:20 UTC
[jira] [Commented] (CARBONDATA-319) Bad Records logging for column
data type is not proper
[ https://issues.apache.org/jira/browse/CARBONDATA-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15578363#comment-15578363 ]
ASF GitHub Bot commented on CARBONDATA-319:
-------------------------------------------
GitHub user sujith71955 opened a pull request:
https://github.com/apache/incubator-carbondata/pull/241
[CARBONDATA-319] Bad Records logging for column data type is not proper
**Problem:**
Bad Records logging for column data type is not proper in case of long, carbon system while creating the table metadata uses BIGINT instead of LONG , internally it converts the bigint to long type and processes , while processing the data if any long type data is having issue it will be logged into the bad record with data type Long which is not proper since as per the metadata the datatype of column is BIGINT.
**Solution :**
Pass name for each data type ENUM constant in constructor, while logging the bad record get the column data type name value from the data type ENUM constant, for LONG the name will be BIGINT.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sujith71955/incubator-carbondata master_BadRecord_Issue
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-carbondata/pull/241.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #241
----
commit 2c08ecdbb50e57afcea26d25d80fe2b7f8208310
Author: sujith71955 <su...@gmail.com>
Date: 2016-10-15T15:39:27Z
[CARBONDATA-319]
Bad Records logging for column data type is not proper in case of long, carbon system while creating the table metadata uses BIGINT instead of LONG , internally it converts the bigint to long type and processes , while processing the data if any long type data is having issue it will be logged into the bad record with data type Long which is not proper since as per the metadata the datatype of column is BIGINT.
----
> Bad Records logging for column data type is not proper
> ------------------------------------------------------
>
> Key: CARBONDATA-319
> URL: https://issues.apache.org/jira/browse/CARBONDATA-319
> Project: CarbonData
> Issue Type: Bug
> Reporter: Sujith
> Assignee: Sujith
> Priority: Minor
>
> Bad Records logging for column data type is not proper in case of long, carbon system while creating the table metadata uses BIGINT instead of LONG , internally it converts the bigint to long type and processes , while processing the data if any long type data is having issue it will be logged into the bad record with data type Long which is not proper since as per the metadata the datatype of column is BIGINT.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)