dev
step 1:create table:
cc.sql("CREATE TABLE IF NOT EXISTS qqdata2.oc_indextest (id STRING,
CUST_ORDER_ID STRING,ORDER_ITEM_IDATTR_ID STRING,TTR_VALUE_IDATTR_VALUE
STRING,CREATE_DATE STRING,UPDATE_DATE STRING,STATUS_CD STRING,STATUS_DATE
STRING,AREA_ID STRING,REGION_CD STRING,UPDATE_STAFF STR
dev
Version: Spark 2.1.1 , carbondata 1.1.1 hadoop 2.7.2
test table:
xitest2 amount of data 2Billion ,
xitemp2 amount of data 0 ,
xitemp amount of data 950
run sql
cc.sql("update xitest2 a set (
a.qqnum,a.nick,a.age,a.gender,a.au
Hi
Can you provide the full script? what is your update script? how to
reproduce ?
Regards
Liang
yixu2001 wrote
> dev
>
> On the process of "update" statement execution, interruption happened.
> After that, the "select" statement failed.
> Sometimes the "select" statement will recover to s
Hi
Can you raise an apache JIRA at :
https://issues.apache.org/jira/projects/CARBONDATA
and provide the test data and script, need to reproduce this issue.
Regards
Liang
刘feng wrote
> Hello,dev
>
>1,When using the ‘like’query in sql, I found a bug.
>
> E.g: select ake005,count(1) from ca_
+1 , i agree with Jacky points.
As we know, carbondata already be able to get very good performance for
filter query scenarios through MDK index. supports pre-aggregate in 1.3.0
would improve aggregated query scenarios. so users can use one carbondata
to support all query cases(both filter and a
Hello,dev
1,When using the ‘like’query in sql, I found a bug.
E.g: select ake005,count(1) from ca_08_kc22 where ake005 like '33011%'
and akc225>10 group by ake005;
Get sample data:
++--+--+
| ake005 | _c1 |
++--+--+
| 33011 | 1