Re: [DISCUSSION] Whether Carbondata should keep carbon-sql-shell script

[Ravindra Pesala]

Hi,

carbon-spark-shell was added to simplify the usage for first time users. I
don't see any problem now of this feature to be removed. It is also simple
code to be maintained. In case in future if this feature need to be
modified because of spark compatible issues we can discuss again.

Regards,
Ravindra.

On 7 June 2017 at 09:42, Erlu Chen  wrote:

> Thanks for correct my mistake.
>
> Yes, Just carbon-spark-shell, I think carbon-spark-sql is more helpful than
> carbon-spark-shell, because it providing a method to interact with
> carbondata via sql command, rather than carbon api.
>
> Based on what I mentioned above, I think carbondata can still keep
> carbon-spark-sql.
>
> Regards.
> Chenerlu.
>
>
>
> --
> View this message in context: http://apache-carbondata-dev-
> mailing-list-archive.1130556.n5.nabble.com/DISCUSSION-
> Whether-Carbondata-should-keep-carbon-spark-shell-
> script-tp14077p14087.html
> Sent from the Apache CarbonData Dev Mailing List archive mailing list
> archive at Nabble.com.
>



-- 
Thanks & Regards,
Ravi

Re: [DISCUSSION] Whether Carbondata should keep carbon-sql-shell script

[Erlu Chen]

Thanks for correct my mistake.

Yes, Just carbon-spark-shell, I think carbon-spark-sql is more helpful than
carbon-spark-shell, because it providing a method to interact with
carbondata via sql command, rather than carbon api.

Based on what I mentioned above, I think carbondata can still keep
carbon-spark-sql.

Regards.
Chenerlu.



--
View this message in context: 
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/DISCUSSION-Whether-Carbondata-should-keep-carbon-spark-shell-script-tp14077p14087.html
Sent from the Apache CarbonData Dev Mailing List archive mailing list archive 
at Nabble.com.

[jira] [Created] (CARBONDATA-1136) After compaction, the select query is not showing data

[QiangCai (JIRA)]

QiangCai created CARBONDATA-1136:


 Summary: After compaction, the select query is not showing data
 Key: CARBONDATA-1136
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1136
 Project: CarbonData
  Issue Type: Bug
Reporter: QiangCai
Assignee: QiangCai


After compaction, the select query is not showing data

create table part_major_compact(a String, b int) partitioned by (c int) stored 
by 'carbondata' tblproperties('PARTITION_TYPE'='LIST','LIST_INFO'='1,2')

insert into part_major_compact select 'a', 2, 3 from originTable limit 1
insert into part_major_compact select 'b', 3, 4 from originTable limit 1
insert into part_major_compact select 'c', 4, 5 from originTable limit 1
insert into part_major_compact select 'd', 1, 2 from originTable limit 1

alter table part_major_compact compact 'major'

select * from part_major_compact where c = 4



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSSION] Whether Carbondata should keep carbon-sql-shell script

[Liang Chen]

Hi

correct the file name, should be : ./bin/carbon-spark-sql and
./bin/carbon-spark-shell.

Are you suggesting removing both file or only carbon-spark-shell ?

Regards
Liang

2017-06-07 0:24 GMT+08:00 Erlu Chen :

> Hi community,
>
> Recently, I viewed the implementation of carbon-sql-shell and tried to
> understand the function of this script.
>
> This script just wrap some steps and provide existing CarbonContext or
> CarbonSession for users  to interact with Carbondata.
>
> I hold my opinion that we can remove this script because this script is
> useless except providing a existing CarbonContext or CarbonSession.
>
> Reasons as below:
> 1. Carbondata now has integration spark1.x and spark2.x, Carbondata should
> refactor carbon-spark-shell every time when spark update.
> 2. After run this script, it will generate redundant folders in project and
> user may forget to remove these folders.
> 3. The CarbonContext or CarbonSession may be created with store path and
> metastore path which user may not want.
>
> I just share my idea about this, we can discuss about whether we should
> keep
> this script.
>
> Thanks.
>
> Regards.
> Chenerlu.
>
>
>
>
>
>
>
> --
> View this message in context: http://apache-carbondata-dev-
> mailing-list-archive.1130556.n5.nabble.com/DISCUSSION-
> Whether-Carbondata-should-keep-carbon-sql-shell-script-tp14077.html
> Sent from the Apache CarbonData Dev Mailing List archive mailing list
> archive at Nabble.com.
>

[DISCUSSION] Whether Carbondata should keep carbon-sql-shell script

[Erlu Chen]

Hi community,

Recently, I viewed the implementation of carbon-sql-shell and tried to
understand the function of this script.

This script just wrap some steps and provide existing CarbonContext or
CarbonSession for users  to interact with Carbondata.

I hold my opinion that we can remove this script because this script is
useless except providing a existing CarbonContext or CarbonSession.

Reasons as below:
1. Carbondata now has integration spark1.x and spark2.x, Carbondata should
refactor carbon-spark-shell every time when spark update.
2. After run this script, it will generate redundant folders in project and
user may forget to remove these folders.
3. The CarbonContext or CarbonSession may be created with store path and
metastore path which user may not want.

I just share my idea about this, we can discuss about whether we should keep
this script.

Thanks.

Regards.
Chenerlu.







--
View this message in context: 
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/DISCUSSION-Whether-Carbondata-should-keep-carbon-sql-shell-script-tp14077.html
Sent from the Apache CarbonData Dev Mailing List archive mailing list archive 
at Nabble.com.

[jira] [Created] (CARBONDATA-1135) Show partition column information in describe formatted command

[Kunal Kapoor (JIRA)]

Kunal Kapoor created CARBONDATA-1135:


 Summary: Show partition column information in describe formatted 
command
 Key: CARBONDATA-1135
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1135
 Project: CarbonData
  Issue Type: Improvement
Reporter: Kunal Kapoor
Assignee: Kunal Kapoor
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CARBONDATA-1134) Generate redundant folders under integration model when run test cases with mvn command in spark1.6

[chenerlu (JIRA)]

chenerlu created CARBONDATA-1134:


 Summary: Generate redundant folders under integration model when 
run test cases with mvn command in spark1.6
 Key: CARBONDATA-1134
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1134
 Project: CarbonData
  Issue Type: Bug
Reporter: chenerlu
Priority: Minor


When run mvn  -Pspark-1.6 -Dspark.version=1.6.3 clean package, it will generate 
redundant  folders under integration model.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CARBONDATA-1133) Executor lost failure in case of data load failure due to bad records

[Manish Gupta (JIRA)]

Manish Gupta created CARBONDATA-1133:


 Summary: Executor lost failure in case of data load failure due to 
bad records
 Key: CARBONDATA-1133
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1133
 Project: CarbonData
  Issue Type: Bug
Reporter: Manish Gupta
Assignee: Manish Gupta
 Fix For: 1.2.0


when we try to do data load with bad records continuously, after some time it 
is observed that executor is lost due to OOM error and application also gets 
restarted by yarn after some time. This happens because in case of data load 
failure due to bad records exception is thrown by the executor and task keeps 
retrying till the max number of retry attempts are reached. This keeps 
happening continuously and after some time application is restarted by yarn.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CARBONDATA-1132) describe formatted query should display SORT_COLUMNS column

[Rahul Kumar (JIRA)]

Rahul Kumar created CARBONDATA-1132:
---

 Summary: describe formatted query should display SORT_COLUMNS 
column
 Key: CARBONDATA-1132
 URL: https://issues.apache.org/jira/browse/CARBONDATA-1132
 Project: CarbonData
  Issue Type: Improvement
Reporter: Rahul Kumar
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)