[jira] [Comment Edited] (CARBONDATA-1788) Insert is not working as expected when loaded with more than 32000 column length.

2017-12-22 Thread pakanati revathi (JIRA)

[ 
https://issues.apache.org/jira/browse/CARBONDATA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301237#comment-16301237
 ] 

pakanati revathi edited comment on CARBONDATA-1788 at 12/22/17 10:30 AM:
-

Used only insert statement with column length >32000


was (Author: revathip):
Used only insert statement.

> Insert is not working as expected when loaded with more than 32000 column 
> length.
> -
>
> Key: CARBONDATA-1788
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1788
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Insert.PNG
>
>
> Insert should accept only 32000 length column. But when trying to load more 
> than 32000 column length data, insert is successful.
> Expected result: When inserted more than 32000 column length, the insert 
> should throw error.
> Actual result: When inserted more than 32000 column length, the insert is 
> successful.
> Note: Update also should throw error while updating more than 3200 column 
> length.Please implement for update also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (CARBONDATA-1788) Insert is not working as expected when loaded with more than 32000 column length.

2017-12-22 Thread pakanati revathi (JIRA)

[ 
https://issues.apache.org/jira/browse/CARBONDATA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301237#comment-16301237
 ] 

pakanati revathi commented on CARBONDATA-1788:
--

Used only insert statement.

> Insert is not working as expected when loaded with more than 32000 column 
> length.
> -
>
> Key: CARBONDATA-1788
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1788
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Insert.PNG
>
>
> Insert should accept only 32000 length column. But when trying to load more 
> than 32000 column length data, insert is successful.
> Expected result: When inserted more than 32000 column length, the insert 
> should throw error.
> Actual result: When inserted more than 32000 column length, the insert is 
> successful.
> Note: Update also should throw error while updating more than 3200 column 
> length.Please implement for update also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (CARBONDATA-1715) Carbon 1.3.0- Datamap BAD_RECORD_ACTION is not working as per the Document link.

2017-12-22 Thread pakanati revathi (JIRA)

[ 
https://issues.apache.org/jira/browse/CARBONDATA-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301219#comment-16301219
 ] 

pakanati revathi commented on CARBONDATA-1715:
--

Verified

> Carbon 1.3.0- Datamap BAD_RECORD_ACTION is not working as per the Document 
> link.
> 
>
> Key: CARBONDATA-1715
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1715
> Project: CarbonData
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Assignee: dhatchayani
>Priority: Minor
>  Labels: Document
> Attachments: Bad_Records.PNG
>
>
> By default the BAD_RECORDS_ACTION = FORCE should be written in 
> "http://carbondata.apache.org/dml-operation-on-carbondata.html; document link 
> but it is written as BAD_RECORDS_ACTION = FAIL.
> Expected result: BAD_RECORDS_ACTION = FORCE should be mentioned BAD RECORDS 
> HANDLING section in document.
> Actual issue: BAD_RECORDS_ACTION = FAIL is present in the Document link.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (CARBONDATA-1715) Carbon 1.3.0- Datamap BAD_RECORD_ACTION is not working as per the Document link.

2017-12-22 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi resolved CARBONDATA-1715.
--
Resolution: Fixed

> Carbon 1.3.0- Datamap BAD_RECORD_ACTION is not working as per the Document 
> link.
> 
>
> Key: CARBONDATA-1715
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1715
> Project: CarbonData
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Assignee: dhatchayani
>Priority: Minor
>  Labels: Document
> Attachments: Bad_Records.PNG
>
>
> By default the BAD_RECORDS_ACTION = FORCE should be written in 
> "http://carbondata.apache.org/dml-operation-on-carbondata.html; document link 
> but it is written as BAD_RECORDS_ACTION = FAIL.
> Expected result: BAD_RECORDS_ACTION = FORCE should be mentioned BAD RECORDS 
> HANDLING section in document.
> Actual issue: BAD_RECORDS_ACTION = FAIL is present in the Document link.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1788) Insert is not working as expected when loaded with more than 32000 column length.

2017-11-21 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1788:
-
Description: 
Insert should accept only 32000 length column. But when trying to load more 
than 32000 column length data, insert is successful.

Expected result: When inserted more than 32000 column length, the insert should 
throw error.
Actual result: When inserted more than 32000 column length, the insert is 
successful.

Note: Update also should throw error while updating more than 3200 column 
length.Please implement for update also.

  was:
Insert should accept only 32000 length column. But when trying to load more 
than 32000 column length data is inserting successfully.

Expected result: When inserted more than 32000 column length, the insert should 
throw error.
Actual result: When inserted more than 32000 column length, the insert is 
successful.

Note: Update also should throw error while updating more than 3200 column 
length.Please implement for update also.


> Insert is not working as expected when loaded with more than 32000 column 
> length.
> -
>
> Key: CARBONDATA-1788
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1788
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Insert.PNG
>
>
> Insert should accept only 32000 length column. But when trying to load more 
> than 32000 column length data, insert is successful.
> Expected result: When inserted more than 32000 column length, the insert 
> should throw error.
> Actual result: When inserted more than 32000 column length, the insert is 
> successful.
> Note: Update also should throw error while updating more than 3200 column 
> length.Please implement for update also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (CARBONDATA-1788) Insert is not working as expected when loaded with more than 32000 column length.

2017-11-21 Thread pakanati revathi (JIRA)
pakanati revathi created CARBONDATA-1788:


 Summary: Insert is not working as expected when loaded with more 
than 32000 column length.
 Key: CARBONDATA-1788
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1788
 Project: CarbonData
  Issue Type: Bug
  Components: sql
Affects Versions: 1.3.0
 Environment: 3 node ant cluster
Reporter: pakanati revathi
Priority: Minor
 Attachments: Insert.PNG

Insert should accept only 32000 length column. But when trying to load more 
than 32000 column length data is inserting successfully.

Expected result: When inserted more than 32000 column length, the insert should 
throw error.
Actual result: When inserted more than 32000 column length, the insert is 
successful.

Note: Update also should throw error while updating more than 3200 column 
length.Please implement for update also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1715) Carbon 1.3.0- Datamap BAD_RECORD_ACTION is not working as per the Document link.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1715:
-
Summary: Carbon 1.3.0- Datamap BAD_RECORD_ACTION is not working as per the 
Document link.  (was: Carbon 1.3.0- Bad Records BAD_RECORD_ACTION is not 
working as per the Document link.)

> Carbon 1.3.0- Datamap BAD_RECORD_ACTION is not working as per the Document 
> link.
> 
>
> Key: CARBONDATA-1715
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1715
> Project: CarbonData
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
>  Labels: Document
> Attachments: Bad_Records.PNG
>
>
> By default the BAD_RECORDS_ACTION = FORCE should be written in 
> "http://carbondata.apache.org/dml-operation-on-carbondata.html; document link 
> but it is written as BAD_RECORDS_ACTION = FAIL.
> Expected result: BAD_RECORDS_ACTION = FORCE should be mentioned BAD RECORDS 
> HANDLING section in document.
> Actual issue: BAD_RECORDS_ACTION = FAIL is present in the Document link.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (CARBONDATA-1716) Carbon 1.3.0-Table Comment- When unset the header is not removed in describe formatted.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi closed CARBONDATA-1716.

Resolution: Invalid

It is UNSETTING to the default behavior where the table comment property is 
provided by default in the desc formatted.

>  Carbon 1.3.0-Table Comment- When unset the header is not removed in describe 
> formatted.
> 
>
> Key: CARBONDATA-1716
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1716
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
>  Labels: Functional
> Attachments: UNSET is not working as expected 1.PNG, UNSET is not 
> working as expected.PNG
>
>
> When UNSET, the header is not removed in the Describe Formatted.
> Create a table with comment.
> SET the comment
> UNSET the comment
> Describe formatted
> Expected Result: When UNSET the header should be removed in the Describe 
> Formatted.
> Actual result: When UNSET the header is not removed in the describe Formatted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (CARBONDATA-1718) carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi closed CARBONDATA-1718.

Resolution: Invalid

Configuration set in property file was not proper. 

> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> --
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: action redirect.PNG, action redirect1.PNG
>
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Summary: carbon.options.bad.records.action=REDIRECT configured in 
carbon.properties is not working as expected.  (was: Carbon 1.3.0 Bad Record 
-carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
not working as expected.)

> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> --
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: action redirect.PNG, action redirect1.PNG
>
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Attachment: (was: action redirect.PNG)

> Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT 
> configured in carbon.properties is not working as expected.
> ---
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: action redirect.PNG, action redirect1.PNG
>
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Attachment: action redirect.PNG

> Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT 
> configured in carbon.properties is not working as expected.
> ---
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: action redirect.PNG, action redirect1.PNG
>
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Attachment: (was: Bad_Record_REDIRECT.PNG)

> Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT 
> configured in carbon.properties is not working as expected.
> ---
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Attachment: (was: Bad_Record_REDIRECT1.PNG)

> Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT 
> configured in carbon.properties is not working as expected.
> ---
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Bad_Record_REDIRECT.PNG
>
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Summary: Carbon 1.3.0 Bad Record 
-carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
not working as expected.  (was: Carbon 1.3.0 Bad Record 
carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
not working as expected.)

> Carbon 1.3.0 Bad Record -carbon.options.bad.records.action=REDIRECT 
> configured in carbon.properties is not working as expected.
> ---
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Bad_Record_REDIRECT.PNG, Bad_Record_REDIRECT1.PNG
>
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Description: 
carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
not working as expected.

When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
csv should be created. But Csv is not created.

Expected Result: When we set carbon properties as 
carbon.options.bad.records.action=REDIRECT , Csv should be created.

Actual Result: When we set carbon properties as 
carbon.options.bad.records.action=REDIRECT , Csv is not  created.





  was:
carbon.options.bad.records.action=REDIRECT is not working as expected.

When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, ideally csv 
should be created. But Csv is not created.

Expected Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv should be created.

Actual Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv is not  created.






> Carbon 1.3.0 Bad Record carbon.options.bad.records.action=REDIRECT configured 
> in carbon.properties is not working as expected.
> --
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Bad_Record_REDIRECT.PNG, Bad_Record_REDIRECT1.PNG
>
>
> carbon.options.bad.records.action=REDIRECT configured in carbon.properties is 
> not working as expected.
> When we set carbon properties as carbon.options.bad.records.action=REDIRECT , 
> csv should be created. But Csv is not created.
> Expected Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv should be created.
> Actual Result: When we set carbon properties as 
> carbon.options.bad.records.action=REDIRECT , Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Description: 
carbon.options.bad.records.action=REDIRECT is not working as expected.

When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, ideally csv 
should be created. But Csv is not created.

Expected Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv should be created.

Actual Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv is not  created.





  was:
BAD_RECORD_ACTION = REDIRECT is not working as expected.

When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, ideally csv 
should be created. But Csv is not created.

Expected Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv should be created.

Actual Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv is not  created.






> Carbon 1.3.0 Bad Record carbon.options.bad.records.action=REDIRECT configured 
> in carbon.properties is not working as expected.
> --
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Bad_Record_REDIRECT.PNG, Bad_Record_REDIRECT1.PNG
>
>
> carbon.options.bad.records.action=REDIRECT is not working as expected.
> When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, ideally csv 
> should be created. But Csv is not created.
> Expected Result: When we set carbon properties as BAD_RECORD_ACTION = 
> REDIRECT, Csv should be created.
> Actual Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
> Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0 Bad Record carbon.options.bad.records.action=REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Summary: Carbon 1.3.0 Bad Record carbon.options.bad.records.action=REDIRECT 
configured in carbon.properties is not working as expected.  (was: Carbon 
1.3.0- BAD_RECORD_ACTION = REDIRECT configured in carbon.properties is not 
working as expected.)

> Carbon 1.3.0 Bad Record carbon.options.bad.records.action=REDIRECT configured 
> in carbon.properties is not working as expected.
> --
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Bad_Record_REDIRECT.PNG, Bad_Record_REDIRECT1.PNG
>
>
> BAD_RECORD_ACTION = REDIRECT is not working as expected.
> When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, ideally csv 
> should be created. But Csv is not created.
> Expected Result: When we set carbon properties as BAD_RECORD_ACTION = 
> REDIRECT, Csv should be created.
> Actual Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
> Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1718) Carbon 1.3.0- BAD_RECORD_ACTION = REDIRECT configured in carbon.properties is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1718:
-
Summary: Carbon 1.3.0- BAD_RECORD_ACTION = REDIRECT configured in 
carbon.properties is not working as expected.  (was: Carbon 1.3.0- 
BAD_RECORD_ACTION = REDIRECT is not working as expected.)

> Carbon 1.3.0- BAD_RECORD_ACTION = REDIRECT configured in carbon.properties is 
> not working as expected.
> --
>
> Key: CARBONDATA-1718
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Bad_Record_REDIRECT.PNG, Bad_Record_REDIRECT1.PNG
>
>
> BAD_RECORD_ACTION = REDIRECT is not working as expected.
> When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, ideally csv 
> should be created. But Csv is not created.
> Expected Result: When we set carbon properties as BAD_RECORD_ACTION = 
> REDIRECT, Csv should be created.
> Actual Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
> Csv is not  created.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (CARBONDATA-1718) Carbon 1.3.0- BAD_RECORD_ACTION = REDIRECT is not working as expected.

2017-11-15 Thread pakanati revathi (JIRA)
pakanati revathi created CARBONDATA-1718:


 Summary: Carbon 1.3.0- BAD_RECORD_ACTION = REDIRECT is not working 
as expected.
 Key: CARBONDATA-1718
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1718
 Project: CarbonData
  Issue Type: Bug
  Components: sql
Affects Versions: 1.3.0
 Environment: 3 node ant cluster
Reporter: pakanati revathi
Priority: Minor
 Attachments: Bad_Record_REDIRECT.PNG, Bad_Record_REDIRECT1.PNG

BAD_RECORD_ACTION = REDIRECT is not working as expected.

When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, ideally csv 
should be created. But Csv is not created.

Expected Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv should be created.

Actual Result: When we set carbon properties as BAD_RECORD_ACTION = REDIRECT, 
Csv is not  created.







--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1715) Carbon 1.3.0- Bad Records BAD_RECORD_ACTION is not working as per the Document link.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1715:
-
Summary: Carbon 1.3.0- Bad Records BAD_RECORD_ACTION is not working as per 
the Document link.  (was: Carbondata_1.3.0- Bad Records BAD_RECORD_ACTION is 
not working as per the Document link.)

> Carbon 1.3.0- Bad Records BAD_RECORD_ACTION is not working as per the 
> Document link.
> 
>
> Key: CARBONDATA-1715
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1715
> Project: CarbonData
>  Issue Type: Bug
>  Components: docs
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: Bad_Records.PNG
>
>
> By default the BAD_RECORDS_ACTION = FORCE should be written in 
> "http://carbondata.apache.org/dml-operation-on-carbondata.html; document link 
> but it is written as BAD_RECORDS_ACTION = FAIL.
> Expected result: BAD_RECORDS_ACTION = FORCE should be mentioned BAD RECORDS 
> HANDLING section in document.
> Actual issue: BAD_RECORDS_ACTION = FAIL is present in the Document link.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (CARBONDATA-1716) Carbon 1.3.0-Table Comment- When unset the header is not removed in describe formatted.

2017-11-15 Thread pakanati revathi (JIRA)

 [ 
https://issues.apache.org/jira/browse/CARBONDATA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

pakanati revathi updated CARBONDATA-1716:
-
Summary:  Carbon 1.3.0-Table Comment- When unset the header is not removed 
in describe formatted.  (was:  Carbondata_1.3.0-Table Comment- When unset the 
header is not removed in describe formatted.)

>  Carbon 1.3.0-Table Comment- When unset the header is not removed in describe 
> formatted.
> 
>
> Key: CARBONDATA-1716
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1716
> Project: CarbonData
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 1.3.0
> Environment: 3 node ant cluster
>Reporter: pakanati revathi
>Priority: Minor
> Attachments: UNSET is not working as expected 1.PNG, UNSET is not 
> working as expected.PNG
>
>
> When UNSET, the header is not removed in the Describe Formatted.
> Create a table with comment.
> SET the comment
> UNSET the comment
> Describe formatted
> Expected Result: When UNSET the header should be removed in the Describe 
> Formatted.
> Actual result: When UNSET the header is not removed in the describe Formatted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (CARBONDATA-1716) Carbondata_1.3.0-Table Comment- When unset the header is not removed in describe formatted.

2017-11-14 Thread pakanati revathi (JIRA)
pakanati revathi created CARBONDATA-1716:


 Summary:  Carbondata_1.3.0-Table Comment- When unset the header is 
not removed in describe formatted.
 Key: CARBONDATA-1716
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1716
 Project: CarbonData
  Issue Type: Bug
  Components: sql
Affects Versions: 1.3.0
 Environment: 3 node ant cluster
Reporter: pakanati revathi
Priority: Minor
 Attachments: UNSET is not working as expected 1.PNG, UNSET is not 
working as expected.PNG

When UNSET, the header is not removed in the Describe Formatted.

Create a table with comment.
SET the comment
UNSET the comment
Describe formatted

Expected Result: When UNSET the header should be removed in the Describe 
Formatted.
Actual result: When UNSET the header is not removed in the describe Formatted.








--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (CARBONDATA-1715) Carbondata_1.3.0- Bad Records BAD_RECORD_ACTION is not working as per the Document link.

2017-11-14 Thread pakanati revathi (JIRA)
pakanati revathi created CARBONDATA-1715:


 Summary: Carbondata_1.3.0- Bad Records BAD_RECORD_ACTION is not 
working as per the Document link.
 Key: CARBONDATA-1715
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1715
 Project: CarbonData
  Issue Type: Bug
  Components: docs
Affects Versions: 1.3.0
 Environment: 3 node ant cluster
Reporter: pakanati revathi
Priority: Minor
 Attachments: Bad_Records.PNG

By default the BAD_RECORDS_ACTION = FORCE should be written in 
"http://carbondata.apache.org/dml-operation-on-carbondata.html; document link 
but it is written as BAD_RECORDS_ACTION = FAIL.

Expected result: BAD_RECORDS_ACTION = FORCE should be mentioned BAD RECORDS 
HANDLING section in document.

Actual issue: BAD_RECORDS_ACTION = FAIL is present in the Document link.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)