[jira] [Created] (KYLIN-2117) support add edit model even cube is ready

2016-10-20 Thread Zhong,Jason (JIRA)
Zhong,Jason created KYLIN-2117:
--

 Summary: support add edit model even cube is ready
 Key: KYLIN-2117
 URL: https://issues.apache.org/jira/browse/KYLIN-2117
 Project: Kylin
  Issue Type: Improvement
  Components: Metadata
Affects Versions: v1.5.4.1
Reporter: Zhong,Jason
Assignee: Shaofeng SHI


now after creating a model and cube, when cube id build to 'READY' status,
we cannot edit model. but user may want to add new column to model.
so it's necessary to support edit model, and check at backend.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: #2 Step Name: Extract Fact Table Distinct Columns output error

2016-10-20 Thread ShaoFeng Shi
Thanks Yubo.

2016-10-21 10:22 GMT+08:00 yubo-...@yolo24.com :

> Hi shao feng,
>
> Following jira is created to track this problem:
>
> https://issues.apache.org/jira/browse/KYLIN-2116
>
> --
> View this message in context: http://apache-kylin.74782.x6.
> nabble.com/2-Step-Name-Extract-Fact-Table-Distinct-Columns-output-error-
> tp6044p6053.html
> Sent from the Apache Kylin mailing list archive at Nabble.com.
>



-- 
Best regards,

Shaofeng Shi 史少锋


How can i choose a cube is insight?

2016-10-20 Thread ????
Hi

I build two cudes which all contain KYLIN_SALES table in a project and use the 
same model,but have some different dimensions and some same dimensions.
When i query some sql, the sql contains some dimensionss, when dimensionss in 
all two cudes, it uses which cudes?
Thanks!

Re: #2 Step Name: Extract Fact Table Distinct Columns output error

2016-10-20 Thread yubo-...@yolo24.com
Hi shao feng,

Following jira is created to track this problem:

https://issues.apache.org/jira/browse/KYLIN-2116

--
View this message in context: 
http://apache-kylin.74782.x6.nabble.com/2-Step-Name-Extract-Fact-Table-Distinct-Columns-output-error-tp6044p6053.html
Sent from the Apache Kylin mailing list archive at Nabble.com.


[jira] [Created] (KYLIN-2116) when hive field delimitor exists in table field values, fields order is wrong

2016-10-20 Thread yubo (JIRA)
yubo created KYLIN-2116:
---

 Summary: when hive field delimitor exists in table field values, 
fields order is wrong
 Key: KYLIN-2116
 URL: https://issues.apache.org/jira/browse/KYLIN-2116
 Project: Kylin
  Issue Type: Bug
  Components: Job Engine
Affects Versions: v1.5.2
Reporter: yubo
Assignee: Dong Li


in #1 step when creating temp hive table,there is delimitor 
 
 ROW FORMAT DELIMITED FIELDS TERMINATED BY '\177' 
 
when this delimitor exists in some fields, fields order is  wrong 


test details:

when we search with same sql, different results are returned as below. 
25 in kylin and 24 in hive. 

We guess there maybe some problem within #2 Step(Extract Fact Table Distinct 
Columns) when building cube. 





1 search in kylin 
 select distinct visit_hour from KYLIN_REPORT_DB.session_behavior_channel_oms 
where  visit_date >= '2016-10-19' and visit_date <= '2016-10-19' 
 Results (25) 
19 
17 
18 
15 
16 
13 
14 
11 
12 
21 
神马搜索 
20 
08 
09 
04 
22 
05 
23 
06 
07 
00 
01 
02 
03 
10 

2. #2 Step Name: Extract Fact Table Distinct Columns output 

hadoop fs -cat 
/kylin/kylin_metadata/kylin-e8bb517d-6c29-4f89-a83e-871e142e3d48/channel_first_stage_flow_cube/fact_distinct_columns/VISIT_HOUR
 
00 
01 
02 
03 
04 
05 
06 
07 
08 
09 
10 
11 
12 
13 
14 
15 
16 
17 
18 
19 
20 
21 
22 
23 
神马搜索 


3. hive table 

hive -e " select distinct visit_hour from 
KYLIN_REPORT_DB.session_behavior_channel_oms where  visit_date >= '2016-10-19' 
and visit_date <= '2016-10-19' " 
WARNING: Use "yarn jar" to launch YARN applications. 

Logging initialized using configuration in 
file:/etc/hive/2.3.4.0-3485/0/hive-log4j.properties 
Query ID = hdfs_20161020164441_dcea3e55-1a8b-4f3a-9378-7dcda008001b 
Total jobs = 1 
Launching Job 1 out of 1 


Status: Running (Executing on YARN cluster with App id 
application_1476342479107_13013) 


 
VERTICES  STATUS  TOTAL  COMPLETED  RUNNING  PENDING  FAILED  
KILLED 

 
Map 1 ..   SUCCEEDED56456400   0   
0 
Reducer 2 ..   SUCCEEDED 15 1500   0   
0 

 
VERTICES: 02/02  [==>>] 100%  ELAPSED TIME: 168.70 s   

 
OK 
03 
12 
13 
22 
05 
14 
08 
17 
00 
02 
18 
06 
23 
01 
19 
07 
10 
15 
20 
16 
11 
04 
09 
21 
Time taken: 172.907 seconds, Fetched: 24 row(s) 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: #2 Step Name: Extract Fact Table Distinct Columns output error

2016-10-20 Thread ShaoFeng Shi
Hi yubo,

Could you please report a JIRA to Kylin?

2016-10-20 18:23 GMT+08:00 yubo-...@yolo24.com :

> thanks for reponse.
>
> we found the cause.
>
> in #1 step when creating temp hive table,there is delimitor
>
> ROW FORMAT DELIMITED FIELDS TERMINATED BY '\177'
>
> unfortunatly, this delimitor exists in some fields.
> that makes the fields order wrong
>
> --
> View this message in context: http://apache-kylin.74782.x6.
> nabble.com/2-Step-Name-Extract-Fact-Table-Distinct-Columns-output-error-
> tp6044p6048.html
> Sent from the Apache Kylin mailing list archive at Nabble.com.
>



-- 
Best regards,

Shaofeng Shi 史少锋


Re: Unable to connect to Kylin Web UI

2016-10-20 Thread Billy(Yiming) Liu
The first thing to do is checking the kylin.log. Is there any exception
when Kylin starts up? Could the sample.sh run successfully?

2016-10-19 19:09 GMT+08:00 Big Data :

> Hi,
>
> I have recently installed kylin 1.5.4.1 Hbase1.x on hortonworks sandbox, I
> am able to connect to Ambari with the address http://127.0.0.1:8080 where
> as I am not able to connect to kylin after successful installation with the
> address http://127.0.0.1:7070/kylin.
>
> I used two n/w adapters both NAT & bridged || Bridged & Bridged and tried
> with port forwarding on NAT with 7070 port but still i am not reachable to
> the web UI.
>
> Kylin sever is restarted successfully.
>
> Appreciate your help.
>



-- 
With Warm regards

Yiming Liu (刘一鸣)


[jira] [Created] (KYLIN-2115) some extended column query returns wrong answer

2016-10-20 Thread Dayue Gao (JIRA)
Dayue Gao created KYLIN-2115:


 Summary: some extended column query returns wrong answer
 Key: KYLIN-2115
 URL: https://issues.apache.org/jira/browse/KYLIN-2115
 Project: Kylin
  Issue Type: Bug
  Components: General
Affects Versions: v1.5.4, v1.5.4.1
Reporter: Dayue Gao
Assignee: Dayue Gao
Priority: Critical


KYLIN-1979 introduces a bug, which can cause extended column query returns 
wrong result if user defines more than one extended column metrics.

{noformat}
Example: let's define two extended columns
1. metricA(host=h1, extend=e1)
2. metricB(host=h2, extend=e2).

"select h1, e1 ... group by h1,e1" correct.
"select h1, e1, h2, e2 ... group by h1,e1, h2, e2" correct.
"select h2, e2 ... group by h2, e2" wrong. (column e2 is empty)

{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: #2 Step Name: Extract Fact Table Distinct Columns output error

2016-10-20 Thread Alberto Ramón
can you chack this post

visit_date <= '2016-10-19'  *==> *visit_date <= DATE'2016-10-19'

2016-10-20 11:07 GMT+02:00 yubo-...@yolo24.com :

>
> hi,
>
> when we search with same sql, different results are returned as below.
> 25 in kylin and 24 in hive.
>
> We guess there maybe some problem within #2 Step(Extract Fact Table
> Distinct
> Columns) when building cube.
>
>
>
>
>
> 1 search in kylin
>  select distinct visit_hour from
> KYLIN_REPORT_DB.session_behavior_channel_oms where  visit_date >=
> '2016-10-19' and visit_date <= '2016-10-19'
>  Results (25)
> 19
> 17
> 18
> 15
> 16
> 13
> 14
> 11
> 12
> 21
> 神马搜索
> 20
> 08
> 09
> 04
> 22
> 05
> 23
> 06
> 07
> 00
> 01
> 02
> 03
> 10
>
> 2. #2 Step Name: Extract Fact Table Distinct Columns output
>
> hadoop fs -cat
> /kylin/kylin_metadata/kylin-e8bb517d-6c29-4f89-a83e-
> 871e142e3d48/channel_first_stage_flow_cube/fact_distinct_
> columns/VISIT_HOUR
> 00
> 01
> 02
> 03
> 04
> 05
> 06
> 07
> 08
> 09
> 10
> 11
> 12
> 13
> 14
> 15
> 16
> 17
> 18
> 19
> 20
> 21
> 22
> 23
> 神马搜索
>
>
> 3. hive table
>
> hive -e " select distinct visit_hour from
> KYLIN_REPORT_DB.session_behavior_channel_oms where  visit_date >=
> '2016-10-19' and visit_date <= '2016-10-19' "
> WARNING: Use "yarn jar" to launch YARN applications.
>
> Logging initialized using configuration in
> file:/etc/hive/2.3.4.0-3485/0/hive-log4j.properties
> Query ID = hdfs_20161020164441_dcea3e55-1a8b-4f3a-9378-7dcda008001b
> Total jobs = 1
> Launching Job 1 out of 1
>
>
> Status: Running (Executing on YARN cluster with App id
> application_1476342479107_13013)
>
> 
> 
> VERTICES  STATUS  TOTAL  COMPLETED  RUNNING  PENDING  FAILED
> KILLED
> 
> 
> Map 1 ..   SUCCEEDED56456400   0
> 0
> Reducer 2 ..   SUCCEEDED 15 1500   0
> 0
> 
> 
> VERTICES: 02/02  [==>>] 100%  ELAPSED TIME: 168.70
> s
> 
> 
> OK
> 03
> 12
> 13
> 22
> 05
> 14
> 08
> 17
> 00
> 02
> 18
> 06
> 23
> 01
> 19
> 07
> 10
> 15
> 20
> 16
> 11
> 04
> 09
> 21
> Time taken: 172.907 seconds, Fetched: 24 row(s)
>
> --
> View this message in context: http://apache-kylin.74782.x6.
> nabble.com/2-Step-Name-Extract-Fact-Table-Distinct-
> Columns-output-error-tp6044.html
> Sent from the Apache Kylin mailing list archive at Nabble.com.
>


#2 Step Name: Extract Fact Table Distinct Columns output error

2016-10-20 Thread yubo-...@yolo24.com

hi,

when we search with same sql, different results are returned as below.
25 in kylin and 24 in hive.

We guess there maybe some problem within #2 Step(Extract Fact Table Distinct
Columns) when building cube.





1 search in kylin 
 select distinct visit_hour from
KYLIN_REPORT_DB.session_behavior_channel_oms where  visit_date >=
'2016-10-19' and visit_date <= '2016-10-19' 
 Results (25)
19
17
18
15
16
13
14
11
12
21
神马搜索
20
08
09
04
22
05
23
06
07
00
01
02
03
10

2. #2 Step Name: Extract Fact Table Distinct Columns output

hadoop fs -cat
/kylin/kylin_metadata/kylin-e8bb517d-6c29-4f89-a83e-871e142e3d48/channel_first_stage_flow_cube/fact_distinct_columns/VISIT_HOUR
00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
神马搜索


3. hive table 

hive -e " select distinct visit_hour from
KYLIN_REPORT_DB.session_behavior_channel_oms where  visit_date >=
'2016-10-19' and visit_date <= '2016-10-19' "
WARNING: Use "yarn jar" to launch YARN applications.

Logging initialized using configuration in
file:/etc/hive/2.3.4.0-3485/0/hive-log4j.properties
Query ID = hdfs_20161020164441_dcea3e55-1a8b-4f3a-9378-7dcda008001b
Total jobs = 1
Launching Job 1 out of 1


Status: Running (Executing on YARN cluster with App id
application_1476342479107_13013)


VERTICES  STATUS  TOTAL  COMPLETED  RUNNING  PENDING  FAILED 
KILLED

Map 1 ..   SUCCEEDED56456400   0  
0
Reducer 2 ..   SUCCEEDED 15 1500   0  
0

VERTICES: 02/02  [==>>] 100%  ELAPSED TIME: 168.70 s   

OK
03
12
13
22
05
14
08
17
00
02
18
06
23
01
19
07
10
15
20
16
11
04
09
21
Time taken: 172.907 seconds, Fetched: 24 row(s)

--
View this message in context: 
http://apache-kylin.74782.x6.nabble.com/2-Step-Name-Extract-Fact-Table-Distinct-Columns-output-error-tp6044.html
Sent from the Apache Kylin mailing list archive at Nabble.com.


Re: [jira] [Created] (KYLIN-2108) Support usage of schema name "default" in SQL

2016-10-20 Thread Alberto Ramón
Nice :)

Improve the interoperability with BI programs sounds great and feels very
important ¡¡
http://mail-archives.apache.org/mod_mbox/kylin-user/201609.mbox/browser

2016-10-19 9:18 GMT+02:00 Yifan Zhang (JIRA) :

> Yifan Zhang created KYLIN-2108:
> --
>
>  Summary: Support usage of schema name "default" in SQL
>  Key: KYLIN-2108
>  URL: https://issues.apache.org/jira/browse/KYLIN-2108
>  Project: Kylin
>   Issue Type: Improvement
>   Components: Query Engine
> Reporter: Yifan Zhang
> Assignee: Yifan Zhang
> Priority: Minor
>
>
> Calcite will treat "DEFAULT" as internal keyword, while "DEFAULT" is also
> used as HIVE's default schema name. We need to escape such case of usage by
> quote it.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>