[jira] [Created] (KYLIN-3906) ExecutableManager is spelled as ExecutableManger

2019-03-25 Thread Yanwen Lin (JIRA)
Yanwen Lin created KYLIN-3906:
-

 Summary: ExecutableManager is spelled as ExecutableManger
 Key: KYLIN-3906
 URL: https://issues.apache.org/jira/browse/KYLIN-3906
 Project: Kylin
  Issue Type: Improvement
  Components: Job Engine
Affects Versions: v3.0.0
Reporter: Yanwen Lin
 Fix For: v3.0.0
 Attachments: KYLIN-3906.patch

As titled, please see attachment for patch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: spark task error occurs when run IT in sanbox

2019-03-25 Thread yuzhang
Hi elkan:
 Thank you take time to reply.
 Just as you said, the reason is the unmatched jdk version. I just set 
root's JAVA_HOME to point jdk1.8, but every server in sandbox has it's own user 
to run it. So I should re-link the original JAVA_HOME to new one.


Best regards 
yuzhang


| |
yuzhang
|
|
shifengdefan...@163.com
|
签名由网易邮箱大师定制
On 3/25/2019 13:32,elkan1788 wrote:
Seems there your Java running time environment was not clean. Please check
the JAVA_HOME and PATH system variable, use the echo command see what output
from them.

By the way the Kylin also can run in Hadoop clusters which use JDK1.7,  just
a simple modify. The steps like this:

1. modify the HBase conf file which name is hbase-env.sh, add export
JAVA_HOME=/path/of/jdk1.8

2. append the below configure into kylin_job_conf.xml and
kylin_job_conf_inmem.xml files.


mapred.child.env
JAVA_HOME=/usr/lib/java/jdk1.8.0_201



yarn.app.mapreduce.am.env
JAVA_HOME=/usr/lib/java/jdk1.8.0_201


Hope those can help you!

--
Sent from: http://apache-kylin.74782.x6.nabble.com/


[jira] [Created] (KYLIN-3907) Sort the cube list by create time in descending order.

2019-03-25 Thread Yuzhang QIU (JIRA)
Yuzhang QIU created KYLIN-3907:
--

 Summary: Sort the cube list by create time in descending order.
 Key: KYLIN-3907
 URL: https://issues.apache.org/jira/browse/KYLIN-3907
 Project: Kylin
  Issue Type: Improvement
  Components: REST Service
Affects Versions: v2.5.2
Reporter: Yuzhang QIU


Hi team:
Maybe there have a use experience problem in the Web UI of cube list. We 
will create many cubes over time and need click "MORE" to show the lastest cube 
when the number cubes increate to over 15.
   In most cases, I think, the older cube should be steady and the new cube may 
need to be debuged. So, sort  the cube list by create time in descending order 
may be better.
How do you think about this?

Best regards
yuzhang



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (KYLIN-3908) KylinClient's HttpRequest.releaseConnection is not needed in retrieveMetaData & executeKylinQuery

2019-03-25 Thread Xiaobo Liao (JIRA)
Xiaobo Liao created KYLIN-3908:
--

 Summary: KylinClient's HttpRequest.releaseConnection is not needed 
in retrieveMetaData &  executeKylinQuery
 Key: KYLIN-3908
 URL: https://issues.apache.org/jira/browse/KYLIN-3908
 Project: Kylin
  Issue Type: Improvement
  Components: Driver - JDBC
Affects Versions: v2.5.2
Reporter: Xiaobo Liao
 Fix For: Future


In Kylin client's code 
[https://github.com/apache/kylin/blob/master/jdbc/src/main/java/org/apache/kylin/jdbc/KylinClient.java]

retrieveMetaData &  executeKylinQuery will call 
HttpRequestBase.releaseConnection() if the HTTP calls are succeeded, but not 
doing so if calls are failed.

According to HttpClient's stack trace, connections are released back to 
connection manager after content is consumed.  So it is not necessary to call 
releaseConnection in retrieveMetaData &  executeKylinQuery. 

Of course calling releaseConnection is not harmful, but the code now looks 
confusing that only calling releaseConnection if responded with 20x. 

 
BasicClientConnectionManager.releaseConnection(ManagedClientConnection, long, 
TimeUnit) line: 194
ManagedClientConnectionImpl.releaseConnection() line: 447
BasicManagedEntity.releaseManagedConnection() line: 201
BasicManagedEntity.streamClosed(InputStream) line: 176
EofSensorInputStream.checkClose() line: 237
EofSensorInputStream.close() line: 186
UTF8StreamJsonParser._closeInput() line: 242
UTF8StreamJsonParser(ParserBase).close() line: 385
ObjectMapper._readMapAndClose(JsonParser, JavaType) line: 3745
ObjectMapper.readValue(InputStream, Class) line: 2796
KylinClient.executeKylinQuery(String, List, 
Map) line: 379
KylinClient.executeQuery(String, List, List, 
Map) line: 326
KylinResultSet.execute() line: 69
AvaticaConnection$1.execute() line: 607
KylinMeta.prepareAndExecute(Meta$StatementHandle, String, long, int, 
Meta$PrepareCallback) line: 111

KylinConnection(AvaticaConnection).prepareAndExecuteInternal(AvaticaStatement, 
String, long) line: 615
KylinStatement(AvaticaStatement).executeInternal(String) line: 148
KylinStatement(AvaticaStatement).executeQuery(String) line: 218



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (KYLIN-3909) kylin job failed for MappeableRunContainer is not registered

2019-03-25 Thread Liu Shaohui (JIRA)
Liu Shaohui created KYLIN-3909:
--

 Summary: kylin job failed for MappeableRunContainer is not 
registered
 Key: KYLIN-3909
 URL: https://issues.apache.org/jira/browse/KYLIN-3909
 Project: Kylin
  Issue Type: Bug
Reporter: Liu Shaohui


|Job aborted due to stage failure: Task 2 in stage 1.0 failed 4 times, most 
recent failure: Lost task 2.3 in stage 1.0 (TID 2621, zjy-hadoop-prc-st2587.bj, 
executor 53): com.esotericsoftware.kryo.KryoException: 
java.lang.IllegalArgumentException: Class is not registered: 
org.apache.kylin.job.shaded.org.roaringbitmap.buffer.MappeableRunContainer|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [DISCUSS] Kylin 3.0 alpha and beta release before GA

2019-03-25 Thread Luke Han
Sounds good

Best Regards!
-

Luke Han


On Mon, Mar 25, 2019 at 9:24 AM ShaoFeng Shi  wrote:

> Hello,
>
> About two months ago, we raised the "[Discuss] Moving toward Apache Kylin
> 3.0" in the developer group, all agree to use 3.0 as the next major release
> version when the Real-Time feature released. Now we're merging the code
> from the RT feature branch into the master branch.
>
> Although this feature has been in production in certain early users, it
> has not been widely evaluated by the community. I would like to propose
> releasing the alpha and beta before the GA release, just like what we did
> in Kylin v2.0. This is to give our users enough time to evaluate; On the
> other side, it gives the developers the time to hear feedback, to improve
> the stability/performance, catch up the documentation and others.
>
> A rough plan is:
> - April, 3.0 alpha release
> - June, 3.0 beta release
> - July to Aug, 3.0 GA release
>
> Before 3.0 GA, the v2.6 branch will roll out bug fix releases at a steady
> pace; Usually, 1 version every 1-2 months, depends on the severity of the
> reported issues.
>
> We warmly welcome the community users to join the 3.0 alpha and beta.
> Please share your comments here. Thank you for the support to Apache Kylin!
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC
> Email: shaofeng...@apache.org
>
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: user-subscr...@kylin.apache.org
> Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>
>
>


Re:[DISCUSS] Kylin 3.0 alpha and beta release before GA

2019-03-25 Thread Ma Gang
Thanks ShaoFeng,


The plan looks good.

At 2019-03-25 09:24:00, "ShaoFeng Shi"  wrote:

Hello,


About two months ago, we raised the "[Discuss] Moving toward Apache Kylin 3.0" 
in the developer group, all agree to use 3.0 as the next major release version 
when the Real-Time feature released. Now we're merging the code from the RT 
feature branch into the master branch. 


Although this feature has been in production in certain early users, it has not 
been widely evaluated by the community. I would like to propose releasing the 
alpha and beta before the GA release, just like what we did in Kylin v2.0. This 
is to give our users enough time to evaluate; On the other side, it gives the 
developers the time to hear feedback, to improve the stability/performance, 
catch up the documentation and others.


A rough plan is:
- April, 3.0 alpha release
- June, 3.0 beta release
- July to Aug, 3.0 GA release


Before 3.0 GA, the v2.6 branch will roll out bug fix releases at a steady pace; 
Usually, 1 version every 1-2 months, depends on the severity of the reported 
issues.


We warmly welcome the community users to join the 3.0 alpha and beta.  Please 
share your comments here. Thank you for the support to Apache Kylin! 


Best regards,


Shaofeng Shi 史少锋
Apache Kylin PMC
Email: shaofeng...@apache.org


Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: user-subscr...@kylin.apache.org
Join Kylin dev mail group: dev-subscr...@kylin.apache.org






[jira] [Created] (KYLIN-3910) Fix missing guava dependency when submit flink application to YARN

2019-03-25 Thread vinoyang (JIRA)
vinoyang created KYLIN-3910:
---

 Summary: Fix missing guava dependency when submit flink 
application to YARN
 Key: KYLIN-3910
 URL: https://issues.apache.org/jira/browse/KYLIN-3910
 Project: Kylin
  Issue Type: Sub-task
  Components: Flink Engine
Reporter: vinoyang
Assignee: vinoyang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [DISCUSS] Kylin 3.0 alpha and beta release before GA

2019-03-25 Thread JiaTao Tao
Seems awesome, looking forward to Kylin 3.0.


-- 


Regards!

Aron Tao

ShaoFeng Shi  于2019年3月25日周一 上午1:24写道:

> Hello,
>
> About two months ago, we raised the "[Discuss] Moving toward Apache Kylin
> 3.0" in the developer group, all agree to use 3.0 as the next major release
> version when the Real-Time feature released. Now we're merging the code
> from the RT feature branch into the master branch.
>
> Although this feature has been in production in certain early users, it has
> not been widely evaluated by the community. I would like to propose
> releasing the alpha and beta before the GA release, just like what we did
> in Kylin v2.0. This is to give our users enough time to evaluate; On the
> other side, it gives the developers the time to hear feedback, to improve
> the stability/performance, catch up the documentation and others.
>
> A rough plan is:
> - April, 3.0 alpha release
> - June, 3.0 beta release
> - July to Aug, 3.0 GA release
>
> Before 3.0 GA, the v2.6 branch will roll out bug fix releases at a steady
> pace; Usually, 1 version every 1-2 months, depends on the severity of the
> reported issues.
>
> We warmly welcome the community users to join the 3.0 alpha and beta.
> Please share your comments here. Thank you for the support to Apache Kylin!
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC
> Email: shaofeng...@apache.org
>
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: user-subscr...@kylin.apache.org
> Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>