[jira] [Updated] (KYLIN-3001) Fix the wrong Cache key issue

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3001:
-
Summary: Fix the wrong Cache key issue   (was: Cache key issue )

> Fix the wrong Cache key issue 
> --
>
> Key: KYLIN-3001
> URL: https://issues.apache.org/jira/browse/KYLIN-3001
> Project: Kylin
>  Issue Type: Bug
>  Components: Query Engine
>Affects Versions: v2.1.0
>Reporter: Pan, Julian
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN_3001_Cache_key_issue.patch
>
>
> Currently the cacheKey generate by SQLRequest getCacheKey:
> cacheKey = Lists.newArrayList(sql.replaceAll("\\s+", ""), project, offset, 
> limit, acceptPartial,
> backdoorToggles);
> Which will remove all the space and break line.
> If I have a sql:
> select a, sum(c) from table 
> --where a > 0 group by a;
> and another sql:
> select a, sum(c) from table 
> --where a > 0 
> group by a;
> The two sql will share same cache key.
> But the first sql should be break. If you query second sql, and then query 
> the first again. It will return result.
> And another issue is if remove all space, which will mix a as b and aasb.
> I think the better way is just replace multiple space to one space
> Should I create a patch? Or just provide the fix:
> cacheKey = Lists.newArrayList(sql.replaceAll("[ ]", " "), project, offset, 
> limit, acceptPartial,
> backdoorToggles);



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

[jira] [Updated] (KYLIN-3004) Update validation when deleting segment

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3004:
-
Summary: Update validation when deleting segment  (was: Delete cube segment 
validation)

> Update validation when deleting segment
> ---
>
> Key: KYLIN-3004
> URL: https://issues.apache.org/jira/browse/KYLIN-3004
> Project: Kylin
>  Issue Type: Bug
>  Components: REST Service
>Affects Versions: v2.1.0
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN_3004.patch, KYLIN_3004.patch
>
>
> In version 2.1, kylin allow hole between segment.
> But currently, there is validation for delete segment.
> Here is the code in CubeService:
>  if (!segmentName.equals(cube.getSegments().get(0).getName())
> && 
> !segmentName.equals(cube.getSegments().get(cube.getSegments().size() - 
> 1).getName())) {
> throw new 
> BadRequestException(String.format(msg.getDELETE_NOT_FIRST_LAST_SEG(), 
> segmentName));
> }
> Does it make sense? Should we remove the limit?



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

[jira] [Updated] (KYLIN-3024) Input Validator for "Auto Merge Thresholds" text box

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3024:
-
Summary: Input Validator for "Auto Merge Thresholds" text box  (was: Limit 
the "Auto Merge Thresholds" text box to be input a negative number)

> Input Validator for "Auto Merge Thresholds" text box
> 
>
> Key: KYLIN-3024
> URL: https://issues.apache.org/jira/browse/KYLIN-3024
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3024-Limit-the-Auto-Merge-Thresholds-text-box-.patch, 
> Auto_merge_thresholds.png
>
>
> When you create a new cube or edit a existent cube, then do as follows
> 1. Open the "Refresh Setting";
> 2. Write one value for "Auto Merge Thresholds" parameter;
> Then you will find the text box can be input negative numbers, which can be 
> summited, it should be invalid.
> Refer to [^Auto_merge_thresholds.png]



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

[jira] [Updated] (KYLIN-3010) Remove v1 Spark engine code

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3010:
-
Issue Type: Task  (was: Improvement)

> Remove v1 Spark engine code
> ---
>
> Key: KYLIN-3010
> URL: https://issues.apache.org/jira/browse/KYLIN-3010
> Project: Kylin
>  Issue Type: Task
>  Components: Spark Engine
>Reporter: Shaofeng SHI
>Assignee: Shaofeng SHI
>Priority: Major
> Fix For: v2.3.0
>
>
> Kylin's first version of Spark engine (in-mem algorithm) wasn't released, and 
> be replaced with the v2 engine (by layer algorithm); It's time to remove it 
> from the codebase.



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

[jira] [Updated] (KYLIN-3024) Limit the "Auto Merge Thresholds" text box to be input a negative number

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3024:
-
Priority: Minor  (was: Major)

> Limit the "Auto Merge Thresholds" text box to be input a negative number
> 
>
> Key: KYLIN-3024
> URL: https://issues.apache.org/jira/browse/KYLIN-3024
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3024-Limit-the-Auto-Merge-Thresholds-text-box-.patch, 
> Auto_merge_thresholds.png
>
>
> When you create a new cube or edit a existent cube, then do as follows
> 1. Open the "Refresh Setting";
> 2. Write one value for "Auto Merge Thresholds" parameter;
> Then you will find the text box can be input negative numbers, which can be 
> summited, it should be invalid.
> Refer to [^Auto_merge_thresholds.png]



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

[jira] [Commented] (KYLIN-3028) Build cube error when set S3 as working-dir

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343037#comment-16343037
 ] 

Billy Liu commented on KYLIN-3028:
--

Hi [~Shaofengshi], what's the root cause here? The "kylin" keyword, or the 
sub-directory? 
To use the EMR, user needs to both kylin.env.hdfs-working-dir and 
kylin.storage.hbase.cluster-fs?

> Build cube error when set S3 as working-dir
> ---
>
> Key: KYLIN-3028
> URL: https://issues.apache.org/jira/browse/KYLIN-3028
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
> Environment: AWS EMR 5.7, Apache Kylin 2.2 for HBase 1.x
>Reporter: Shaofeng SHI
>Assignee: Shaofeng SHI
>Priority: Minor
> Fix For: v2.3.0
>
>
> 1. Start an AWS EMR cluster, with HBase selected (data stored on S3);
> 2. Download and expand apache-kylin-2.2 for hbase 1.x binary package on EMR 
> 5.7's master node. Copy the "hbase.zookeeper.quorum" property from 
> /etc/hbase/conf/hbase-site.xml to $KYLIN_HOME/conf/kylin_job_conf.xml;  In 
> kylin.properties, set: "kylin.env.hdfs-working-dir=s3://mybucket/kylin"
> 3. Build the sample cube, in the job failed at "Create HTable" step, error is:
> {code}
> 2017-11-10 08:21:35,011 DEBUG [http-bio-7070-exec-2] 
> cachesync.Broadcaster:290 : Done broadcastingUPDATE, cube, kylin_sales_cube
> 2017-11-10 08:21:35,013 ERROR [Scheduler 1778356018 Job 
> 5a2893c9-3a76-458c-a03e-5cd97839fca5-393] common.HadoopShellExecutable:64 : 
> error execute 
> HadoopShellExecutable{id=5a2893c9-3a76-458c-a03e-5cd97839fca5-05, name=Create 
> HTable, state=RUNNING}
> org.apache.hadoop.security.AccessControlException: Permission denied: 
> user=root, access=WRITE, 
> inode="/kylin/kylin_metadata/kylin-5a2893c9-3a76-458c-a03e-5cd97839fca5/kylin_sales_cube/rowkey_stats":hdfs:hadoop:drwxr-xr-x
> at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:320)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1728)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1712)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1695)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
> at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:3896)
> at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:984)
> at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:622)
> at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2049)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2045)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1698)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2045)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at 
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
> at 
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73)
> at 
> org.apache.hadoop.hdfs.DFSClient.primitiveMkdir(DFSClient.java:3002)
> at org.apache.hadoop.hdfs.DFSClient.mkdirs(DFSClient.java:2970)
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem$21.doCall(DistributedFileSystem.java:1047)
> at 
> 

[jira] [Resolved] (KYLIN-3047) Wrong column type when sync hive table via beeline

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3047.
--
Resolution: Fixed

> Wrong column type when sync hive table via beeline
> --
>
> Key: KYLIN-3047
> URL: https://issues.apache.org/jira/browse/KYLIN-3047
> Project: Kylin
>  Issue Type: Bug
>Reporter: liyang
>Assignee: Wang Cheng
>Priority: Major
>  Labels: scope
> Fix For: v2.3.0
>
>
> Thanks chenglong.fu  reporting this issue. Below 
> quotes from his email.
> The origin table looks like:
> {code}
> 75is_scenechar(2) 客户是否在现场
> 76reference_code  varchar(50) 推荐人代码
> 77reference_jgcodevarchar(50) 推荐人机构代码
> 78applicationagreementbarcode varchar(50) 领用合约代码
> 79remakes varchar(1000)   备注信息
> 80data_idnchar(1) 数据标示C－渠道，D－直销
> 81source_type varchar(20) 源系统
> 82lst_up_time timestamp   上一次更新日期
> 83data_date   date数据日期 
> {code}
> After import, it becomes in Kylin:
> {code}
> 62IS_CERT_ALL char(256)   2   
> 63IS_SCENEchar(256)   4   客户是否在现场 
> 64REFERENCE_CODE  varchar(256)33  推荐人代码 
> 65REFERENCE_JGCODEvarchar(256)16  推荐人机构代码 
> 66APPLICATIONAGREEMENTBARCODE varchar(256)12504   领用合约代码 
> 67REMAKES varchar(256)2   备注信息 
> 68DATA_IDNchar(256)   2   数据标示C－渠道，D－直销 
> 69SOURCE_TYPE varchar(256)2   源系统 
> 70LST_UP_TIME timestamp   1   上一次更新日期 
> 71DATA_DATE   date1   数据日期
> {code}
> Code analysis leads to {{org.apache.kylin.source.hive.BeelineHiveClient}}:
> {code}
> public HiveTableMeta getHiveTableMeta(String database, String tableName) 
> throws SQLException {
> ResultSet columns = metaData.getColumns(null, database, tableName, null);
> HiveTableMetaBuilder builder = new HiveTableMetaBuilder();
> builder.setTableName(tableName);
> List allColumns = Lists.newArrayList();
> while (columns.next()) {
> allColumns.add(new 
> HiveTableMeta.HiveTableColumnMeta(columns.getString(4), columns.getString(6), 
> columns.getString(12)));
> }
> builder.setAllColumns(allColumns);
> DBUtils.closeQuietly(columns);
> stmt.execute("use " + database);
> ResultSet resultSet = stmt.executeQuery("describe formatted " + 
> tableName);
> extractHiveTableMeta(resultSet, builder);
> DBUtils.closeQuietly(resultSet);
> return builder.createHiveTableMeta();
> }
> {code}



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

[jira] [Updated] (KYLIN-3114) Enable kylin.web.query-timeout for web query request

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3114:
-
Summary: Enable kylin.web.query-timeout for web query request  (was: Make 
timeout for the queries submitted through the Web UI configurable)

> Enable kylin.web.query-timeout for web query request
> 
>
> Key: KYLIN-3114
> URL: https://issues.apache.org/jira/browse/KYLIN-3114
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.2.0
> Environment: HDP 2.5.6, Kylin 2.2.0
>Reporter: Vsevolod Ostapenko
>Assignee: Vsevolod Ostapenko
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: KYLIN-3114.master.002.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently query.js hard codes timeout for the queries submitted via Web UI to 
> be 300_000 milliseconds.
> Depending on the situation, the default value can be either too large, or too 
> small, especially when query does not hit any cube and is passed through to 
> Hive or Impala.
> Query timeout should be made configurable via kylin.properties.



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

[jira] [Resolved] (KYLIN-3124) Support horizontal scroll bar in 'Insight'

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3124.
--
Resolution: Fixed

> Support horizontal scroll bar in 'Insight'
> --
>
> Key: KYLIN-3124
> URL: https://issues.apache.org/jira/browse/KYLIN-3124
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.2.0
> Environment: Windows , Chrome Version 63.0.3239.108,Firefox 57.0.2 
>Reporter: atul
>Assignee: Zhixiong Chen
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: horizontal_scrollbar_missing.jpg
>
>
> As attached in screenshot, ,due to missing scrollbar in Kylin Web UI  
> (http://:7070/kylin/query) , it's difficult to view full name of cube 
> after executing query from "Insight" view of UI.



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

[jira] [Commented] (KYLIN-3182) Update Kylin help menu links

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342996#comment-16342996
 ] 

Billy Liu commented on KYLIN-3182:
--

Thanks [~Zhixiong Chen], I will update the links to docs23 later. 

> Update Kylin help menu links
> 
>
> Key: KYLIN-3182
> URL: https://issues.apache.org/jira/browse/KYLIN-3182
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: Zhixiong Chen
>Priority: Minor
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 0001-KYLIN-3182-Kylin-Help-is-not-available.patch, 
> 0001-KYLIN-3182-complete-web-help-configuration.patch, help_blank.png
>
>
> Kylin Help is not available, look like
>   !help_blank.png! 
> Then I analyse the web code, and find the problem.
> The default help informations have been configured in the 
> 'kylin-defaults.properties', as follow
> {code:java}
> kylin.web.help.length=4
> kylin.web.help.0=start|Getting Started|
> kylin.web.help.1=odbc|ODBC Driver|
> kylin.web.help.2=tableau|Tableau Guide|
> kylin.web.help.3=onboard|Cube Design Tutorial|
> {code}
> The all links haven't been configured, but the web page will judge whether 
> the link is empty, if the link is empty, the item under the 'Help' will not 
> be showed.
> So I modified the web code, if the link of help document is null, it will be 
> discarded, not transformed to header page.



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

[jira] [Updated] (KYLIN-3207) Add blog Superset integrate Kylin

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3207:
-
Fix Version/s: v2.3.0

> Add blog Superset integrate Kylin
> -
>
> Key: KYLIN-3207
> URL: https://issues.apache.org/jira/browse/KYLIN-3207
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yongjie zhao
>Assignee: yongjie zhao
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: 0001-Add-blog-superset-with-kylin.patch
>
>
> Add blog Superset integrate Kylin



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

[jira] [Updated] (KYLIN-3208) How to enable custom rule

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3208:
-
Issue Type: New Feature  (was: Improvement)

> How to enable custom rule
> -
>
> Key: KYLIN-3208
> URL: https://issues.apache.org/jira/browse/KYLIN-3208
> Project: Kylin
>  Issue Type: New Feature
>  Components: Job Engine
>Affects Versions: v2.1.0
>Reporter: Manoj kumar
>Assignee: Shaofeng SHI
>Priority: Major
>
> -    How to enable to custom rule for Data transformation - while 
> creating the data model, There should be some way user Define the rules on 
> data being selected. Before building the cube, some rules needs to be applied 
> based on User. Most of OLAP solution like ESSBASE/T1M does provide this 
> features.
> -    Entitlement of Data - How to do that in Kylin.



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

[jira] [Assigned] (KYLIN-3206) Consider SQL expression aggregation when applying limit push down

[Billy Liu (JIRA)]

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

Billy Liu reassigned KYLIN-3206:


Assignee: Paul Lin  (was: liyang)

> Consider SQL expression aggregation when applying limit push down
> -
>
> Key: KYLIN-3206
> URL: https://issues.apache.org/jira/browse/KYLIN-3206
> Project: Kylin
>  Issue Type: Bug
>  Components: Query Engine
>Affects Versions: v1.6.0, v2.2.0
> Environment: Kylin 1.6.0
>Reporter: Paul Lin
>Assignee: Paul Lin
>Priority: Major
>
> SQLs like "select floor(user_level /10), sum(money) group by floor(user_level 
> /10) limit 10"  should not trigger storage limit push down, because the 
> expressions like "floor(user_level /10)" are sort of post aggregations. 
> Otherwise Kylin would do aggregations based on partial records, producing 
> inaccurate results. 
>  



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

[jira] [Resolved] (KYLIN-3202) Doc directory for 2.3

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3202.
--
   Resolution: Fixed
 Assignee: Billy Liu
Fix Version/s: v2.3.0

Commit: http://git-wip-us.apache.org/repos/asf/kylin/commit/40a53fe3

> Doc directory for 2.3
> -
>
> Key: KYLIN-3202
> URL: https://issues.apache.org/jira/browse/KYLIN-3202
> Project: Kylin
>  Issue Type: Sub-task
>Reporter: Billy Liu
>Assignee: Billy Liu
>Priority: Major
> Fix For: v2.3.0
>
>




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

[jira] [Assigned] (KYLIN-3198) More Chinese Howto Documents

[Billy Liu (JIRA)]

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

Billy Liu reassigned KYLIN-3198:


Assignee: Paul Lin

> More Chinese Howto Documents
> 
>
> Key: KYLIN-3198
> URL: https://issues.apache.org/jira/browse/KYLIN-3198
> Project: Kylin
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Billy Liu
>Assignee: Paul Lin
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: 80.patch
>
>
> From [https://github.com/apache/kylin/pull/80]
> Five how to documents are added:
>  
> {{[added Chinese version of 
> howto_optimize_build|https://github.com/apache/kylin/pull/80/commits/25206674f9eda19417a3c5d5f15dae8adcdb6952]}}
>  
> {{[added Chinese version of 
> howto_backup_metadata|https://github.com/apache/kylin/pull/80/commits/e773c00b030c29a79419403a86430715f1be57c3]}}
>  
> [added Chinese version of 
> howto_build_cube_with_restapi|https://github.com/apache/kylin/pull/80/commits/087fb355b74f34cd9cc345ad4c3d76df11fd3c97]
>  
> {{[added Chinese version of 
> howto_cleanup_storage|https://github.com/apache/kylin/pull/80/commits/7f2c690267b5a2b8c459e3ad07691c280ffd4e8c]}}
>  
> {{[added Chinese version of 
> howto_jdbc|https://github.com/apache/kylin/pull/80/commits/38477271eed350d9576f484b414ddf2576d54d06]}}



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

[jira] [Resolved] (KYLIN-3175) Streaming segment lost TSRange after merge

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3175.
--
Resolution: Fixed

> Streaming segment lost TSRange after merge
> --
>
> Key: KYLIN-3175
> URL: https://issues.apache.org/jira/browse/KYLIN-3175
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Assignee: Wang Cheng
>Priority: Major
> Fix For: v2.3.0
>
>
> After merging streaming cube's segments, the final merged segment's TSRange 
> is set to null and won't be updated, which causes it's start time/end time to 
> be ZERO(1970-01-01).



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

[jira] [Updated] (KYLIN-3175) Streaming segment lost TSRange after merge

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3175:
-
Fix Version/s: v2.3.0

> Streaming segment lost TSRange after merge
> --
>
> Key: KYLIN-3175
> URL: https://issues.apache.org/jira/browse/KYLIN-3175
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Assignee: Wang Cheng
>Priority: Major
> Fix For: v2.3.0
>
>
> After merging streaming cube's segments, the final merged segment's TSRange 
> is set to null and won't be updated, which causes it's start time/end time to 
> be ZERO(1970-01-01).



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

[jira] [Reopened] (KYLIN-3175) Streaming segment lost TSRange after merge

[Billy Liu (JIRA)]

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

Billy Liu reopened KYLIN-3175:
--

Commit: 
https://github.com/apache/kylin/commit/16236ef30cde20e474740fdee693ce26dbd88155

> Streaming segment lost TSRange after merge
> --
>
> Key: KYLIN-3175
> URL: https://issues.apache.org/jira/browse/KYLIN-3175
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Assignee: Wang Cheng
>Priority: Major
>
> After merging streaming cube's segments, the final merged segment's TSRange 
> is set to null and won't be updated, which causes it's start time/end time to 
> be ZERO(1970-01-01).



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

[jira] [Comment Edited] (KYLIN-3172) No such file or directory error with CreateLookupHiveViewMaterializationStep

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342189#comment-16342189
 ] 

Billy Liu edited comment on KYLIN-3172 at 1/27/18 3:36 PM:
---

Commit: 
https://github.com/apache/kylin/commit/35979ff0875d06cb4b1cc4b151efe6af37d1318d


was (Author: yimingliu):
Commit: 
https://github.com/apache/kylin/commit/0ae39b5bb1cb05d3660ffb94c125cd8e85b91902

> No such file or directory error with CreateLookupHiveViewMaterializationStep 
> -
>
> Key: KYLIN-3172
> URL: https://issues.apache.org/jira/browse/KYLIN-3172
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Major
> Fix For: v2.3.0
>
>
> No such file or directory error for CreateLookupHiveViewMaterializationStep 
> with kylin cluster mode
> error describe:
> ../tomcat/temp/beeline_6287823046370163072.hql (No such file or directory)



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

[jira] [Resolved] (KYLIN-3173) DefaultScheduler shutdown didn't reset field initialized.

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3173.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/195fdef501ee03f5e31fdae81d282f3e0cf1ee0f

> DefaultScheduler shutdown didn't reset field initialized.
> -
>
> Key: KYLIN-3173
> URL: https://issues.apache.org/jira/browse/KYLIN-3173
> Project: Kylin
>  Issue Type: Bug
>Reporter: jiatao.tao
>Assignee: jiatao.tao
>Priority: Minor
> Fix For: v2.3.0
>
>




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

[jira] [Resolved] (KYLIN-2876) Ineffective check in ExternalAclProvider

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-2876.
--
   Resolution: Fixed
Fix Version/s: v2.3.0

Commit: 
https://github.com/apache/kylin/commit/a31bce69dfef5ee8070e8b642cdcfbcfde404a60

> Ineffective check in ExternalAclProvider
> 
>
> Key: KYLIN-2876
> URL: https://issues.apache.org/jira/browse/KYLIN-2876
> Project: Kylin
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: jiatao.tao
>Priority: Major
> Fix For: v2.3.0
>
>
> {code}
> if (inited)
> return singleton;
> synchronized (ExternalAclProvider.class) {
> if (inited)
> return singleton;
> {code}
> If one thread assigns inited but without initialization complete, another 
> thread may read the value of inited being true and use the partial result.



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

[jira] [Resolved] (KYLIN-3167) Datatype lost precision when using beeline

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3167.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/55365b68dfa021f5c14acbd79e2417f55b294473

> Datatype lost precision when using beeline
> --
>
> Key: KYLIN-3167
> URL: https://issues.apache.org/jira/browse/KYLIN-3167
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Assignee: Wang Cheng
>Priority: Major
> Fix For: v2.3.0
>
>
> When using beeline to retrieve Hive table meta information, KYLIN only pick 
> up the datatype's name, for example:
> varchar(1000) -> varchar
> decimal(9,4) -> decimal
> char(10) -> char
> In later processing, KYLIN append default precision for those datatypes, it 
> is inconsistent with originals.
>  



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

[jira] [Resolved] (KYLIN-3172) No such file or directory error with CreateLookupHiveViewMaterializationStep

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3172.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/0ae39b5bb1cb05d3660ffb94c125cd8e85b91902

> No such file or directory error with CreateLookupHiveViewMaterializationStep 
> -
>
> Key: KYLIN-3172
> URL: https://issues.apache.org/jira/browse/KYLIN-3172
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Major
> Fix For: v2.3.0
>
>
> No such file or directory error for CreateLookupHiveViewMaterializationStep 
> with kylin cluster mode
> error describe:
> ../tomcat/temp/beeline_6287823046370163072.hql (No such file or directory)



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

[jira] [Commented] (KYLIN-3135) Fix regular expression bug in SQL comments

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342187#comment-16342187
 ] 

Billy Liu commented on KYLIN-3135:
--

One more commit on this issue: 
https://github.com/apache/kylin/commit/7d5fb855064e2b81cd3b154cdeeafec4e64f63c9

> Fix regular expression bug in SQL comments
> --
>
> Key: KYLIN-3135
> URL: https://issues.apache.org/jira/browse/KYLIN-3135
> Project: Kylin
>  Issue Type: Bug
>Reporter: hahayuan
>Assignee: hahayuan
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: 0001-KYLIN-3135.patch
>
>
> Hi,all.
> Recently,I was testing query function of kylin,
> sometimes I just comment with /**/ instead of delete the sql,cause I need to 
> query and compare again.
> And I was confused that the results says it was "No Support Sql",but it can 
> query success without comments.
> For example,
> {code:java}
> /*
> select count(*) from kylin_sales;
> */
> select * from kylin_sales;
> {code}
> So I view the code and find the commentPatterns of  /\**/  was 
> {code:java}
> /\\*[^\\*/]*
> {code}
> ,clearly it was wrong.
> The regular expression of [abc] means any character in abc,such as a or b.
> So the [^\\*/] means that * or / can't appear,
> But under this circumstances the */ need to be as a string not separated 
> character.
> the */ can't appear not * or / can't appear.
> I rewrite the regular expression,
> {code:java}
> /\\*[\\s\\S]*?\\*/
> {code}
> if you think it's necessary to change the old code,please review and replace 
> it.
> Thank for you time.



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

[jira] [Resolved] (KYLIN-3158) Metadata broadcast should only retry failed node

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3158.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/baf7133dabd8f1e53f5235b61da2bc5da334d870

> Metadata broadcast should only retry failed node
> 
>
> Key: KYLIN-3158
> URL: https://issues.apache.org/jira/browse/KYLIN-3158
> Project: Kylin
>  Issue Type: Improvement
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> In commit 
> https://github.com/apache/kylin/commit/ecc01458c4ad361aaf863505884d51474a8fec9d,
>  Kylin starts to retry failed metadata sync event, however it re-posts the 
> failed event to all nodes. The retry SHOULD only apply to the failed node 
> only.



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

[jira] [Resolved] (KYLIN-3164) HBase connection must be closed when clearing connection pool

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3164.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/9dfd8b9c8a5ad4b185f9855b7ef167087f06d2a1

> HBase connection must be closed when clearing connection pool
> -
>
> Key: KYLIN-3164
> URL: https://issues.apache.org/jira/browse/KYLIN-3164
> Project: Kylin
>  Issue Type: Bug
>Reporter: liyang
>Assignee: liyang
>Priority: Minor
> Fix For: v2.3.0
>
>
> Currently {{HBaseConnection.clearConnCache()}} does not invoke {{close()}} on 
> hbase connections. But it should.



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

[jira] [Resolved] (KYLIN-3157) Enhance query timeout to entire query life cycle

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3157.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/1f33dd93123dd59795a16193a3b5064419f4b532

> Enhance query timeout to entire query life cycle
> 
>
> Key: KYLIN-3157
> URL: https://issues.apache.org/jira/browse/KYLIN-3157
> Project: Kylin
>  Issue Type: Improvement
>Reporter: jiatao.tao
>Assignee: jiatao.tao
>Priority: Major
> Fix For: v2.3.0
>
>
> Nowadays, kylin's query timeout( kylin.query.timeout-seconds ) is only for 
> one OLAP context, should be for the entire query life cycle.



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

[jira] [Resolved] (KYLIN-3144) Adopt Collections.emptyList() for empty list values

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3144.
--
   Resolution: Fixed
Fix Version/s: v2.3.0

Commit: 
https://github.com/apache/kylin/commit/87a0058d9188d4e1140470e0df260548ade097a1

> Adopt Collections.emptyList() for empty list values
> ---
>
> Key: KYLIN-3144
> URL: https://issues.apache.org/jira/browse/KYLIN-3144
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: jiatao.tao
>Priority: Minor
> Fix For: v2.3.0
>
>
> Use Collection.emptyList() for returning an empty list instead of returning 
> new ArrayList<>().
> The default constructor creates a buffer of size 10 for ArrayList . 
> Therefore, returning this static value saves some memory and lessens GC 
> pressure.
> One candidate for replacement is in HybridService#listHybrids()



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

[jira] [Resolved] (KYLIN-3083) potential overflow in CubeHBaseRPC#getCoprocessorTimeoutMillis

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3083.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/5bf5099e15cf732f4b3061743558fb4508ef

> potential overflow in CubeHBaseRPC#getCoprocessorTimeoutMillis
> --
>
> Key: KYLIN-3083
> URL: https://issues.apache.org/jira/browse/KYLIN-3083
> Project: Kylin
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: jiatao.tao
>Priority: Minor
> Fix For: v2.3.0
>
>
> {code}
> } else {
> coopTimeout = 
> cubeSeg.getConfig().getQueryCoprocessorTimeoutSeconds() * 1000;
> {code}
> Two integers are multiplied whose result is expected to be long.
> The operand should be cast to long first.



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

[jira] [Resolved] (KYLIN-3150) Support different compression in PercentileCounter measure

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3150.
--
Resolution: Fixed

Commit: 
https://github.com/apache/kylin/commit/f73219c07f5f0d5e01d801aeb274af9cf886f261

> Support different compression in PercentileCounter measure
> --
>
> Key: KYLIN-3150
> URL: https://issues.apache.org/jira/browse/KYLIN-3150
> Project: Kylin
>  Issue Type: Improvement
>  Components: Query Engine
>Affects Versions: v2.2.0
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Major
> Fix For: v2.3.0
>
>
> With Percentile 1000, the count size more than 10 * 1024. We should use 
> different max length with different compression.



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

[jira] [Assigned] (KYLIN-2836) Lack of synchronization in CodahaleMetrics#close

[Billy Liu (JIRA)]

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

Billy Liu reassigned KYLIN-2836:


Assignee: Jrex Ge

> Lack of synchronization in CodahaleMetrics#close
> 
>
> Key: KYLIN-2836
> URL: https://issues.apache.org/jira/browse/KYLIN-2836
> Project: Kylin
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Jrex Ge
>Priority: Minor
> Fix For: v2.3.0
>
>
> {code}
> timers.invalidateAll();
> {code}
> In other places, timersLock is involved.
> Similar issue for accessing counters and meters.



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

[jira] [Resolved] (KYLIN-2836) Lack of synchronization in CodahaleMetrics#close

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-2836.
--
   Resolution: Fixed
Fix Version/s: v2.3.0

Commit: 
https://github.com/apache/kylin/commit/ebc53b6b72dcade8f0c9f88f36f3aa43a43ae8f8

> Lack of synchronization in CodahaleMetrics#close
> 
>
> Key: KYLIN-2836
> URL: https://issues.apache.org/jira/browse/KYLIN-2836
> Project: Kylin
>  Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
> Fix For: v2.3.0
>
>
> {code}
> timers.invalidateAll();
> {code}
> In other places, timersLock is involved.
> Similar issue for accessing counters and meters.



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

[jira] [Created] (KYLIN-3202) Doc directory for 2.3

[Billy Liu (JIRA)]

Billy Liu created KYLIN-3202:


 Summary: Doc directory for 2.3
 Key: KYLIN-3202
 URL: https://issues.apache.org/jira/browse/KYLIN-3202
 Project: Kylin
  Issue Type: Sub-task
Reporter: Billy Liu






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

[jira] [Resolved] (KYLIN-3200) Enable SonarCloud for Code Analysis

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-3200.
--
   Resolution: Fixed
Fix Version/s: v2.3.0

Commit: [http://git-wip-us.apache.org/repos/asf/kylin/commit/d30d2a30]

We could check the Sonar result from 
[https://sonarcloud.io/dashboard?id=org.apache.kylin%3Akylin]

 

 

> Enable SonarCloud for Code Analysis
> ---
>
> Key: KYLIN-3200
> URL: https://issues.apache.org/jira/browse/KYLIN-3200
> Project: Kylin
>  Issue Type: Task
>Reporter: Billy Liu
>Assignee: Billy Liu
>Priority: Major
> Fix For: v2.3.0
>
>
> [https://sonarcloud.io|https://sonarcloud.io/] is one of the most popular 
> Code Analysis online service. It could integrate with Travis very well. 
> Developer could check the code coverage/bugs/vulnerabilities more easily. 



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

[jira] [Created] (KYLIN-3200) Enable SonarCloud for Code Analysis

[Billy Liu (JIRA)]

Billy Liu created KYLIN-3200:


 Summary: Enable SonarCloud for Code Analysis
 Key: KYLIN-3200
 URL: https://issues.apache.org/jira/browse/KYLIN-3200
 Project: Kylin
  Issue Type: Task
Reporter: Billy Liu
Assignee: Billy Liu


[https://sonarcloud.io|https://sonarcloud.io/] is one of the most popular Code 
Analysis online service. It could integrate with Travis very well. Developer 
could check the code coverage/bugs/vulnerabilities more easily. 



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

[jira] [Resolved] (KYLIN-2556) Switch Findbugs to Spotbugs

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-2556.
--
   Resolution: Fixed
Fix Version/s: (was: Backlog)
   v2.3.0

> Switch Findbugs to Spotbugs
> ---
>
> Key: KYLIN-2556
> URL: https://issues.apache.org/jira/browse/KYLIN-2556
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Shaofeng SHI
>Priority: Major
> Fix For: v2.3.0
>
>
> HADOOP-14316 added Spotbugs which is more powerful than findbugs.
> This issue is to introduce Spotbugs to Kylin in a similar manner.



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

[jira] [Commented] (KYLIN-2556) Switch Findbugs to Spotbugs

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340625#comment-16340625
 ] 

Billy Liu commented on KYLIN-2556:
--

Hi [~Shaofengshi] I'm not sure why your commit is missing. I do the similar 
thing to switch the findbugs to spotbugs. 

https://github.com/apache/kylin/commit/b361844ce16ec01d4c78290a450ff705d0c84911

> Switch Findbugs to Spotbugs
> ---
>
> Key: KYLIN-2556
> URL: https://issues.apache.org/jira/browse/KYLIN-2556
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Shaofeng SHI
>Priority: Major
> Fix For: Backlog
>
>
> HADOOP-14316 added Spotbugs which is more powerful than findbugs.
> This issue is to introduce Spotbugs to Kylin in a similar manner.



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

[jira] [Updated] (KYLIN-2556) Switch Findbugs to Spotbugs

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-2556:
-
Summary: Switch Findbugs to Spotbugs  (was: Introduce Spotbugs)

> Switch Findbugs to Spotbugs
> ---
>
> Key: KYLIN-2556
> URL: https://issues.apache.org/jira/browse/KYLIN-2556
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Shaofeng SHI
>Priority: Major
> Fix For: Backlog
>
>
> HADOOP-14316 added Spotbugs which is more powerful than findbugs.
> This issue is to introduce Spotbugs to Kylin in a similar manner.



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

[jira] [Updated] (KYLIN-3198) More Chinese Howto Documents

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3198:
-
Attachment: 80.patch

> More Chinese Howto Documents
> 
>
> Key: KYLIN-3198
> URL: https://issues.apache.org/jira/browse/KYLIN-3198
> Project: Kylin
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Billy Liu
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: 80.patch
>
>
> From [https://github.com/apache/kylin/pull/80]
> Five how to documents are added:
>  
> {{[added Chinese version of 
> howto_optimize_build|https://github.com/apache/kylin/pull/80/commits/25206674f9eda19417a3c5d5f15dae8adcdb6952]}}
>  
> {{[added Chinese version of 
> howto_backup_metadata|https://github.com/apache/kylin/pull/80/commits/e773c00b030c29a79419403a86430715f1be57c3]}}
>  
> [added Chinese version of 
> howto_build_cube_with_restapi|https://github.com/apache/kylin/pull/80/commits/087fb355b74f34cd9cc345ad4c3d76df11fd3c97]
>  
> {{[added Chinese version of 
> howto_cleanup_storage|https://github.com/apache/kylin/pull/80/commits/7f2c690267b5a2b8c459e3ad07691c280ffd4e8c]}}
>  
> {{[added Chinese version of 
> howto_jdbc|https://github.com/apache/kylin/pull/80/commits/38477271eed350d9576f484b414ddf2576d54d06]}}



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

[jira] [Created] (KYLIN-3198) More Chinese Howto Documents

[Billy Liu (JIRA)]

Billy Liu created KYLIN-3198:


 Summary: More Chinese Howto Documents
 Key: KYLIN-3198
 URL: https://issues.apache.org/jira/browse/KYLIN-3198
 Project: Kylin
  Issue Type: Improvement
  Components: Documentation
Reporter: Billy Liu
 Fix For: v2.3.0


>From [https://github.com/apache/kylin/pull/80]

Five how to documents are added:
 
{{[added Chinese version of 
howto_optimize_build|https://github.com/apache/kylin/pull/80/commits/25206674f9eda19417a3c5d5f15dae8adcdb6952]}}
 
{{[added Chinese version of 
howto_backup_metadata|https://github.com/apache/kylin/pull/80/commits/e773c00b030c29a79419403a86430715f1be57c3]}}
 
[added Chinese version of 
howto_build_cube_with_restapi|https://github.com/apache/kylin/pull/80/commits/087fb355b74f34cd9cc345ad4c3d76df11fd3c97]
 
{{[added Chinese version of 
howto_cleanup_storage|https://github.com/apache/kylin/pull/80/commits/7f2c690267b5a2b8c459e3ad07691c280ffd4e8c]}}
 
{{[added Chinese version of 
howto_jdbc|https://github.com/apache/kylin/pull/80/commits/38477271eed350d9576f484b414ddf2576d54d06]}}



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

[jira] [Closed] (KYLIN-2828) Project meta should be involved for Spark Cubing

[Billy Liu (JIRA)]

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

Billy Liu closed KYLIN-2828.


> Project meta should be involved for Spark Cubing
> 
>
> Key: KYLIN-2828
> URL: https://issues.apache.org/jira/browse/KYLIN-2828
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Assignee: Wang Cheng
>Priority: Minor
> Fix For: v2.2.0
>
>
> java.lang.IllegalStateException: Error to load 
> /model_desc/ci_inner_join_model.json
>   at 
> org.apache.kylin.metadata.MetadataManager.reloadDataModelDescAt(MetadataManager.java:633)
>   at 
> org.apache.kylin.metadata.MetadataManager.reloadAllDataModel(MetadataManager.java:611)
>   at 
> org.apache.kylin.metadata.MetadataManager.init(MetadataManager.java:323)
>   at 
> org.apache.kylin.metadata.MetadataManager.(MetadataManager.java:136)
>   at 
> org.apache.kylin.metadata.MetadataManager.getInstance(MetadataManager.java:94)
>   at org.apache.kylin.cube.model.CubeDesc.init(CubeDesc.java:589)
>   at 
> org.apache.kylin.cube.CubeDescManager.loadCubeDesc(CubeDescManager.java:196)
>   at 
> org.apache.kylin.cube.CubeDescManager.reloadAllCubeDesc(CubeDescManager.java:321)
>   at 
> org.apache.kylin.cube.CubeDescManager.(CubeDescManager.java:114)
>   at 
> org.apache.kylin.cube.CubeDescManager.getInstance(CubeDescManager.java:81)
>   at 
> org.apache.kylin.cube.CubeManager.reloadCubeLocalAt(CubeManager.java:809)
>   at 
> org.apache.kylin.cube.CubeManager.loadAllCubeInstance(CubeManager.java:787)
>   at org.apache.kylin.cube.CubeManager.(CubeManager.java:147)
>   at org.apache.kylin.cube.CubeManager.getInstance(CubeManager.java:105)
>   at 
> org.apache.kylin.engine.spark.SparkCubingByLayer$EncodeBaseCuboid.call(SparkCubingByLayer.java:295)
>   at 
> org.apache.kylin.engine.spark.SparkCubingByLayer$EncodeBaseCuboid.call(SparkCubingByLayer.java:276)
>   at 
> org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1043)
>   at 
> org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1043)
>   at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
>   at 
> org.apache.spark.util.collection.ExternalSorter.insertAll(ExternalSorter.scala:193)
>   at 
> org.apache.spark.shuffle.sort.SortShuffleWriter.write(SortShuffleWriter.scala:63)
>   at 
> org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:96)
>   at 
> org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:53)
>   at org.apache.spark.scheduler.Task.run(Task.scala:99)
>   at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:322)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)



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

[jira] [Resolved] (KYLIN-2828) Project meta should be involved for Spark Cubing

[Billy Liu (JIRA)]

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

Billy Liu resolved KYLIN-2828.
--
   Resolution: Fixed
Fix Version/s: v2.2.0

> Project meta should be involved for Spark Cubing
> 
>
> Key: KYLIN-2828
> URL: https://issues.apache.org/jira/browse/KYLIN-2828
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Assignee: Wang Cheng
>Priority: Minor
> Fix For: v2.2.0
>
>
> java.lang.IllegalStateException: Error to load 
> /model_desc/ci_inner_join_model.json
>   at 
> org.apache.kylin.metadata.MetadataManager.reloadDataModelDescAt(MetadataManager.java:633)
>   at 
> org.apache.kylin.metadata.MetadataManager.reloadAllDataModel(MetadataManager.java:611)
>   at 
> org.apache.kylin.metadata.MetadataManager.init(MetadataManager.java:323)
>   at 
> org.apache.kylin.metadata.MetadataManager.(MetadataManager.java:136)
>   at 
> org.apache.kylin.metadata.MetadataManager.getInstance(MetadataManager.java:94)
>   at org.apache.kylin.cube.model.CubeDesc.init(CubeDesc.java:589)
>   at 
> org.apache.kylin.cube.CubeDescManager.loadCubeDesc(CubeDescManager.java:196)
>   at 
> org.apache.kylin.cube.CubeDescManager.reloadAllCubeDesc(CubeDescManager.java:321)
>   at 
> org.apache.kylin.cube.CubeDescManager.(CubeDescManager.java:114)
>   at 
> org.apache.kylin.cube.CubeDescManager.getInstance(CubeDescManager.java:81)
>   at 
> org.apache.kylin.cube.CubeManager.reloadCubeLocalAt(CubeManager.java:809)
>   at 
> org.apache.kylin.cube.CubeManager.loadAllCubeInstance(CubeManager.java:787)
>   at org.apache.kylin.cube.CubeManager.(CubeManager.java:147)
>   at org.apache.kylin.cube.CubeManager.getInstance(CubeManager.java:105)
>   at 
> org.apache.kylin.engine.spark.SparkCubingByLayer$EncodeBaseCuboid.call(SparkCubingByLayer.java:295)
>   at 
> org.apache.kylin.engine.spark.SparkCubingByLayer$EncodeBaseCuboid.call(SparkCubingByLayer.java:276)
>   at 
> org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1043)
>   at 
> org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1043)
>   at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
>   at 
> org.apache.spark.util.collection.ExternalSorter.insertAll(ExternalSorter.scala:193)
>   at 
> org.apache.spark.shuffle.sort.SortShuffleWriter.write(SortShuffleWriter.scala:63)
>   at 
> org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:96)
>   at 
> org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:53)
>   at org.apache.spark.scheduler.Task.run(Task.scala:99)
>   at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:322)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)



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

[jira] [Reopened] (KYLIN-2828) Project meta should be involved for Spark Cubing

[Billy Liu (JIRA)]

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

Billy Liu reopened KYLIN-2828:
--

> Project meta should be involved for Spark Cubing
> 
>
> Key: KYLIN-2828
> URL: https://issues.apache.org/jira/browse/KYLIN-2828
> Project: Kylin
>  Issue Type: Bug
>Reporter: Wang Cheng
>Assignee: Wang Cheng
>Priority: Minor
> Fix For: v2.2.0
>
>
> java.lang.IllegalStateException: Error to load 
> /model_desc/ci_inner_join_model.json
>   at 
> org.apache.kylin.metadata.MetadataManager.reloadDataModelDescAt(MetadataManager.java:633)
>   at 
> org.apache.kylin.metadata.MetadataManager.reloadAllDataModel(MetadataManager.java:611)
>   at 
> org.apache.kylin.metadata.MetadataManager.init(MetadataManager.java:323)
>   at 
> org.apache.kylin.metadata.MetadataManager.(MetadataManager.java:136)
>   at 
> org.apache.kylin.metadata.MetadataManager.getInstance(MetadataManager.java:94)
>   at org.apache.kylin.cube.model.CubeDesc.init(CubeDesc.java:589)
>   at 
> org.apache.kylin.cube.CubeDescManager.loadCubeDesc(CubeDescManager.java:196)
>   at 
> org.apache.kylin.cube.CubeDescManager.reloadAllCubeDesc(CubeDescManager.java:321)
>   at 
> org.apache.kylin.cube.CubeDescManager.(CubeDescManager.java:114)
>   at 
> org.apache.kylin.cube.CubeDescManager.getInstance(CubeDescManager.java:81)
>   at 
> org.apache.kylin.cube.CubeManager.reloadCubeLocalAt(CubeManager.java:809)
>   at 
> org.apache.kylin.cube.CubeManager.loadAllCubeInstance(CubeManager.java:787)
>   at org.apache.kylin.cube.CubeManager.(CubeManager.java:147)
>   at org.apache.kylin.cube.CubeManager.getInstance(CubeManager.java:105)
>   at 
> org.apache.kylin.engine.spark.SparkCubingByLayer$EncodeBaseCuboid.call(SparkCubingByLayer.java:295)
>   at 
> org.apache.kylin.engine.spark.SparkCubingByLayer$EncodeBaseCuboid.call(SparkCubingByLayer.java:276)
>   at 
> org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1043)
>   at 
> org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1043)
>   at scala.collection.Iterator$$anon$11.next(Iterator.scala:409)
>   at 
> org.apache.spark.util.collection.ExternalSorter.insertAll(ExternalSorter.scala:193)
>   at 
> org.apache.spark.shuffle.sort.SortShuffleWriter.write(SortShuffleWriter.scala:63)
>   at 
> org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:96)
>   at 
> org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:53)
>   at org.apache.spark.scheduler.Task.run(Task.scala:99)
>   at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:322)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)



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

[jira] [Updated] (KYLIN-2776) New metric framework based on dropwizard

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-2776:
-
Summary: New metric framework based on dropwizard  (was: Using dropwizard 
as default metric framework)

> New metric framework based on dropwizard
> 
>
> Key: KYLIN-2776
> URL: https://issues.apache.org/jira/browse/KYLIN-2776
> Project: Kylin
>  Issue Type: New Feature
>Affects Versions: v2.0.0
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-2776.patch, active_calls.png, calls.png, 
> metric_structure.png, query_count.png, query_duration.png, 
> query_result_rowcount.png, report.json
>
>
> With https://issues.apache.org/jira/browse/KYLIN-2721.We are plan to release 
> a new metric framework. 
> New metric is different hadoop metric  and based on dropwizard . which has 
> the following advantage:
> * Well-defined metric model for frequently-needed metrics (ie JVM metrics)
> * Well-defined measurements for all metrics (ie max, mean, stddev, 
> mean_rate, etc),
> * Built-in pluggable reporting frameworks like JMX, Console, Log, JSON 
> We refactored QueryMetric with new metrics, notice the exposed JMX MBeans 
> have changed a little bit.
> A new tool called perflog is also introduced. Perflog traces call duration 
> time  and current active calls by recording them to metric system.
>  Some snapshots of the new JMX MBeans can be seen in attachments



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

[jira] [Commented] (KYLIN-2846) Add a config of hbase namespace for cube storage

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339137#comment-16339137
 ] 

Billy Liu commented on KYLIN-2846:
--

'kylin.storage.hbase.namespace' is introduced to config the hbase namespace, 
the default value is 'default'

> Add a config of hbase namespace for cube storage
> 
>
> Key: KYLIN-2846
> URL: https://issues.apache.org/jira/browse/KYLIN-2846
> Project: Kylin
>  Issue Type: New Feature
>  Components: Storage - HBase
>Affects Versions: v2.1.0
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Minor
>  Labels: scope
> Fix For: v2.3.0
>
> Attachments: KYLIN-2846-001-addium.patch, KYLIN-2846-001.patch, 
> kYLIN-2846-001-cleanhtable.patch
>
>
> In multi-tenancy HBase cluster, namespace is important for quota management 
> and permission control. So we add a global configuration of hbase namespace 
> for cube storage.



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

[jira] [Commented] (KYLIN-2902) Introduce project-level query number control

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339132#comment-16339132
 ] 

Billy Liu commented on KYLIN-2902:
--

'kylin.query.project-concurrent-running-threshold' is introduced to limit the 
concurrent queries for each project. The default value is 20. 

> Introduce project-level query number control
> 
>
> Key: KYLIN-2902
> URL: https://issues.apache.org/jira/browse/KYLIN-2902
> Project: Kylin
>  Issue Type: New Feature
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-2902-refined.patch, APACHE-KYLIN-2902.patch
>
>
> One kylin server may contain many projects. To avoid some projects occupying 
> too much resources, like http connection, project-level query number limit is 
> useful.



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

[jira] [Updated] (KYLIN-2902) Introduce project-level concurrent query number control

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-2902:
-
Summary: Introduce project-level concurrent query number control  (was: 
Introduce project-level query number control)

> Introduce project-level concurrent query number control
> ---
>
> Key: KYLIN-2902
> URL: https://issues.apache.org/jira/browse/KYLIN-2902
> Project: Kylin
>  Issue Type: New Feature
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-2902-refined.patch, APACHE-KYLIN-2902.patch
>
>
> One kylin server may contain many projects. To avoid some projects occupying 
> too much resources, like http connection, project-level query number limit is 
> useful.



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

[jira] [Updated] (KYLIN-2470) cube build failed when 0 bytes input for non-partition fact table

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-2470:
-
Summary: cube build failed when 0 bytes input for non-partition fact table  
(was: cube build failed when no records matching the segment time range)

> cube build failed when 0 bytes input for non-partition fact table
> -
>
> Key: KYLIN-2470
> URL: https://issues.apache.org/jira/browse/KYLIN-2470
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v1.6.0
> Environment: hadoop2.7.3 hive2.1.1 hbase1.2.4 
> apache-kylin-1.6.0-hbase1.x-bin
>Reporter: zhou degao
>Assignee: liyang
>Priority: Major
>  Labels: newbie
> Fix For: v2.3.0
>
>
> I hope the build will be successful then there is no hive data partitions.
> ERRORS are:
> java.lang.IllegalArgumentException: Map input splits are 0 bytes, something 
> is wrong!
>   at 
> org.apache.kylin.engine.mr.common.AbstractHadoopJob.getTotalMapInputMB(AbstractHadoopJob.java:555)
>   at 
> org.apache.kylin.engine.mr.steps.CuboidJob.setReduceTaskNum(CuboidJob.java:175)
>   at org.apache.kylin.engine.mr.steps.CuboidJob.run(CuboidJob.java:138)
>   at org.apache.kylin.engine.mr.MRUtil.runMRJob(MRUtil.java:92)
>   at 
> org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:120)
>   at 
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:113)
>   at 
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:57)
>   at 
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:113)
>   at 
> org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:136)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> result code:2
> In another environment 
> (hadoop2.6.4,hive1.2.1,hbase1.1.3,apache-kylin-1.6.0-hbase1.x-bin) the cube 
> build is successful if there is no hive data partitions from start time to 
> end time .



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

[jira] [Updated] (KYLIN-2470) cube build failed when no records matching the segment time range

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-2470:
-
Issue Type: Bug  (was: Wish)

> cube build failed when no records matching the segment time range
> -
>
> Key: KYLIN-2470
> URL: https://issues.apache.org/jira/browse/KYLIN-2470
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v1.6.0
> Environment: hadoop2.7.3 hive2.1.1 hbase1.2.4 
> apache-kylin-1.6.0-hbase1.x-bin
>Reporter: zhou degao
>Assignee: liyang
>Priority: Major
>  Labels: newbie
> Fix For: v2.3.0
>
>
> I hope the build will be successful then there is no hive data partitions.
> ERRORS are:
> java.lang.IllegalArgumentException: Map input splits are 0 bytes, something 
> is wrong!
>   at 
> org.apache.kylin.engine.mr.common.AbstractHadoopJob.getTotalMapInputMB(AbstractHadoopJob.java:555)
>   at 
> org.apache.kylin.engine.mr.steps.CuboidJob.setReduceTaskNum(CuboidJob.java:175)
>   at org.apache.kylin.engine.mr.steps.CuboidJob.run(CuboidJob.java:138)
>   at org.apache.kylin.engine.mr.MRUtil.runMRJob(MRUtil.java:92)
>   at 
> org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:120)
>   at 
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:113)
>   at 
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:57)
>   at 
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:113)
>   at 
> org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:136)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> result code:2
> In another environment 
> (hadoop2.6.4,hive1.2.1,hbase1.1.3,apache-kylin-1.6.0-hbase1.x-bin) the cube 
> build is successful if there is no hive data partitions from start time to 
> end time .



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

[jira] [Updated] (KYLIN-3044) Support SQL Server as data source

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3044:
-
Issue Type: New Feature  (was: Task)

> Support SQL Server as data source
> -
>
> Key: KYLIN-3044
> URL: https://issues.apache.org/jira/browse/KYLIN-3044
> Project: Kylin
>  Issue Type: New Feature
>Reporter:  Kaige Liu
>Assignee:  Kaige Liu
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3044-sqlserver-as-datasource.patch
>
>
> [KYLIN-1351|https://issues.apache.org/jira/browse/KYLIN-1351] has added 
> Vertica as data source. Base on the work of KYLIN-1351, I'd like to enable 
> SQL Server as data source of kylin.



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

[jira] [Commented] (KYLIN-3055) NullPointerException in MutableRoaringBitmap.or

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339128#comment-16339128
 ] 

Billy Liu commented on KYLIN-3055:
--

Hello [~yuchuqian] Could you update the Jira title to make it easier to read? 

> NullPointerException in MutableRoaringBitmap.or
> ---
>
> Key: KYLIN-3055
> URL: https://issues.apache.org/jira/browse/KYLIN-3055
> Project: Kylin
>  Issue Type: Bug
>Affects Versions: v2.2.0
>Reporter: yuchuqian
>Assignee: yuchuqian
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3055.patch
>
>
> 2017-11-21 19:55:17,363 ERROR [Query 
> b1fbcd45-6524-4b1e-8844-1d6d6277a1bf-120] service.QueryService:459 : 
> Exception while executing query
> java.sql.SQLException: Error while executing SQL "select part_dt,
> intersect_count(item_count, part_dt, array[date'2012-01-01']) as first_day,
> intersect_count(item_count, part_dt, array[date'2012-01-02']) as second_day,
> intersect_count(item_count, part_dt, array[date'2012-01-03']) as third_day,
> intersect_count(item_count, part_dt, 
> array[date'2012-01-01',date'2012-01-02']) as retention_oneday,
> intersect_count(item_count, part_dt, 
> array[date'2012-01-01',date'2012-01-02',date'2012-01-03']) as retention_twoday
> from kylin_sales
> where part_dt in (date'2012-01-01',date'2012-01-02',date'2012-01-03')
> group by PART_DT
> LIMIT 5": null
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at 
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:156)
> at 
> org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:218)
> at org.apache.kylin.rest.service.QueryService.execute(QueryService.java:834)
> at 
> org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:561)
> at org.apache.kylin.rest.service.QueryService.query(QueryService.java:181)
> at 
> org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:415)
> at 
> org.apache.kylin.rest.controller.QueryController.query(QueryController.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at 
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205)
> ..
> Caused by: java.lang.NullPointerException
> at 
> org.roaringbitmap.buffer.MutableRoaringBitmap.or(MutableRoaringBitmap.java:1041)
> at 
> org.apache.kylin.measure.bitmap.RoaringBitmapCounter.orWith(RoaringBitmapCounter.java:72)
> at 
> org.apache.kylin.measure.bitmap.BitmapIntersectDistinctCountAggFunc$RetentionPartialResult.add(BitmapIntersectDistinctCountAggFunc.java:57)
> at 
> org.apache.kylin.measure.bitmap.BitmapIntersectDistinctCountAggFunc.add(BitmapIntersectDistinctCountAggFunc.java:90)
> at Baz$4.apply(ANONYMOUS.java:136)
> at Baz$4.apply(ANONYMOUS.java:158)
> at Baz$4.apply(ANONYMOUS.java)
> at 
> org.apache.calcite.linq4j.EnumerableDefaults.groupBy_(EnumerableDefaults.java:832)
> at 
> org.apache.calcite.linq4j.EnumerableDefaults.groupBy(EnumerableDefaults.java:761)
> at 
> org.apache.calcite.linq4j.DefaultEnumerable.groupBy(DefaultEnumerable.java:302)
> at Baz.bind(Baz.java:99)
> How to re-produce:
> 1. run $KYLIN_HOME/bin/sample.sh 
> 2. then create a cube like 
> {
>   "uuid": "9554f6f6-74dc-489e-b780-2f48f281576c",
>   "last_modified": 1511247707372,
>   "version": "2.2.0.0",
>   "name": "test",
>   "is_draft": false,
>   "model_name": "kylin_sales_model",
>   "description": "",
>   "null_string": null,
>   "dimensions": [
> {
>   "name": "PART_DT",
>   "table": "KYLIN_SALES",
>   "column": "PART_DT",
>   "derived": null
> },
> {
>   "name": "LEAF_CATEG_ID",
>   "table": "KYLIN_SALES",
>   "column": "LEAF_CATEG_ID",
>   "derived": null
> },
> {
>   "name": "LSTG_SITE_ID",
>   "table": "KYLIN_SALES",
>   "column": "LSTG_SITE_ID",
>   "derived": null
> },
> {
>   "name": "CAL_DT",
>   "table": "KYLIN_CAL_DT",
>   "column": null,
>   "derived": [
> "CAL_DT"
>   ]
> },
> {
>   "name": "LEAF_CATEG_ID",
>   "table": "KYLIN_CATEGORY_GROUPINGS",
>   "column": null,
>   "derived": [
> "LEAF_CATEG_ID"
>   ]
> },
> {
>   "name": "USER_DEFINED_FIELD1",
>   "table": "KYLIN_CATEGORY_GROUPINGS",
>   "column": null,
>   "derived": [
> "USER_DEFINED_FIELD1"
>   ]
> },
> {
>   "name": "USER_DEFINED_FIELD3",
>   

[jira] [Updated] (KYLIN-3056) Fix 'Cannot find segment null' bug when click 'SQL' in the cube view page

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3056:
-
Summary: Fix 'Cannot find segment null' bug when click 'SQL' in the cube 
view page  (was: get sql return error in cube view page)

> Fix 'Cannot find segment null' bug when click 'SQL' in the cube view page
> -
>
> Key: KYLIN-3056
> URL: https://issues.apache.org/jira/browse/KYLIN-3056
> Project: Kylin
>  Issue Type: Bug
>  Components: REST Service
>Affects Versions: v2.2.0
>Reporter: Zhixiong Chen
>Assignee: nichunen
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3056.patch, MG337.jpeg
>
>
> In cube view page,if you click 'SQL'.
> The front-end show 'Cannot find segment null'
> !MG337.jpeg!



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

[jira] [Updated] (KYLIN-3064) Turn off Yarn timeline-service when submit mr job

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3064:
-
Summary: Turn off Yarn timeline-service when submit mr job  (was: Turn off 
Yarn timeline-service will start jersey client when submit mr job, remove it)

> Turn off Yarn timeline-service when submit mr job
> -
>
> Key: KYLIN-3064
> URL: https://issues.apache.org/jira/browse/KYLIN-3064
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Minor
> Fix For: v2.3.0
>
>
> We not used timeline service, when the yarn.timeline-service.enabled is true, 
> yarn client will start a jersey client, it will use many resources.



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

[jira] [Updated] (KYLIN-3064) Remove Yarn timeline-service will start jersey client when submit mr job, remove it

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3064:
-
Summary: Remove Yarn timeline-service will start jersey client when submit 
mr job, remove it  (was: Yarn timeline-service will start jersey client when 
submit mr job, remove it)

> Remove Yarn timeline-service will start jersey client when submit mr job, 
> remove it
> ---
>
> Key: KYLIN-3064
> URL: https://issues.apache.org/jira/browse/KYLIN-3064
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Minor
> Fix For: v2.3.0
>
>
> We not used timeline service, when the yarn.timeline-service.enabled is true, 
> yarn client will start a jersey client, it will use many resources.



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

[jira] [Updated] (KYLIN-3064) Turn off Yarn timeline-service will start jersey client when submit mr job, remove it

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3064:
-
Summary: Turn off Yarn timeline-service will start jersey client when 
submit mr job, remove it  (was: Remove Yarn timeline-service will start jersey 
client when submit mr job, remove it)

> Turn off Yarn timeline-service will start jersey client when submit mr job, 
> remove it
> -
>
> Key: KYLIN-3064
> URL: https://issues.apache.org/jira/browse/KYLIN-3064
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Minor
> Fix For: v2.3.0
>
>
> We not used timeline service, when the yarn.timeline-service.enabled is true, 
> yarn client will start a jersey client, it will use many resources.



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

[jira] [Updated] (KYLIN-3064) Yarn timeline-service will start jersey client when submit mr job, remove it

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3064:
-
Issue Type: Improvement  (was: Bug)

> Yarn timeline-service will start jersey client when submit mr job, remove it
> 
>
> Key: KYLIN-3064
> URL: https://issues.apache.org/jira/browse/KYLIN-3064
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Minor
> Fix For: v2.3.0
>
>
> We not used timeline service, when the yarn.timeline-service.enabled is true, 
> yarn client will start a jersey client, it will use many resources.



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

[jira] [Updated] (KYLIN-3068) Rename deprecated parameter for HDFS block size in HiveColumnCardinalityJob

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3068:
-
Summary: Rename deprecated parameter for HDFS block size in 
HiveColumnCardinalityJob  (was: HiveColumnCardinalityJob.java is using 
deprecated parameter name for HDFS block size)

> Rename deprecated parameter for HDFS block size in HiveColumnCardinalityJob
> ---
>
> Key: KYLIN-3068
> URL: https://issues.apache.org/jira/browse/KYLIN-3068
> Project: Kylin
>  Issue Type: Task
>  Components: Job Engine
>Affects Versions: v2.2.0
> Environment: HDP 2.5.3, Kylin 2.2.0
>Reporter: Vsevolod Ostapenko
>Assignee: Vsevolod Ostapenko
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: KYLIN-3068.master.001.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> While setting MR job configuration HiveColumnCardinalityJob.java uses 
> deprecated parameter name for HDFS block size.
> Since Hadoop 2.5 (at least) recommended parameter name is dfs.blocksize, 
> while the existing code (2.2.0 and earlier) uses dfs.block.size (please refer 
> to the list of Hadoop deprecated parameters - 
> http://hadoop.apache.org/docs/r2.7.3/hadoop-project-dist/hadoop-common/DeprecatedProperties.html)



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

[jira] [Updated] (KYLIN-3068) HiveColumnCardinalityJob.java is using deprecated parameter name for HDFS block size

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3068:
-
Issue Type: Task  (was: Bug)

> HiveColumnCardinalityJob.java is using deprecated parameter name for HDFS 
> block size
> 
>
> Key: KYLIN-3068
> URL: https://issues.apache.org/jira/browse/KYLIN-3068
> Project: Kylin
>  Issue Type: Task
>  Components: Job Engine
>Affects Versions: v2.2.0
> Environment: HDP 2.5.3, Kylin 2.2.0
>Reporter: Vsevolod Ostapenko
>Assignee: Vsevolod Ostapenko
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: KYLIN-3068.master.001.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> While setting MR job configuration HiveColumnCardinalityJob.java uses 
> deprecated parameter name for HDFS block size.
> Since Hadoop 2.5 (at least) recommended parameter name is dfs.blocksize, 
> while the existing code (2.2.0 and earlier) uses dfs.block.size (please refer 
> to the list of Hadoop deprecated parameters - 
> http://hadoop.apache.org/docs/r2.7.3/hadoop-project-dist/hadoop-common/DeprecatedProperties.html)



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

[jira] [Updated] (KYLIN-3070) Enable 'kylin.source.hive.flat-table-storage-format' for flat table storage format

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3070:
-
Summary: Enable 'kylin.source.hive.flat-table-storage-format' for flat 
table storage format  (was: Add a config property for flat table storage format)

> Enable 'kylin.source.hive.flat-table-storage-format' for flat table storage 
> format
> --
>
> Key: KYLIN-3070
> URL: https://issues.apache.org/jira/browse/KYLIN-3070
> Project: Kylin
>  Issue Type: Improvement
>  Components: Job Engine
>Affects Versions: v2.2.0
> Environment: HDP 2.5.6, Kylin 2.2.0
>Reporter: Vsevolod Ostapenko
>Assignee: Vsevolod Ostapenko
>Priority: Minor
>  Labels: newbie
> Fix For: v2.3.0
>
> Attachments: KYLIN-3070.master.001.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Flat table storage format is currently hard-coded as SEQUENCEFILE in the 
> core-job/src/main/java/org/apache/kylin/job/JoinedFlatTable.java
> That prevents using Impala as a SQL engine while using beeline CLI (via 
> custom JDBC URL), as Impala cannot write sequence files.
> Adding a parameter to kylin.properties to override the default setting would 
> address the issue.
> Removing a hard-coded value for storage format might be good idea in and on 
> itself.



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

[jira] [Updated] (KYLIN-3070) Enable 'kylin.source.hive.flat-table-storage-format' for flat table storage format

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3070:
-
Priority: Major  (was: Minor)

> Enable 'kylin.source.hive.flat-table-storage-format' for flat table storage 
> format
> --
>
> Key: KYLIN-3070
> URL: https://issues.apache.org/jira/browse/KYLIN-3070
> Project: Kylin
>  Issue Type: Improvement
>  Components: Job Engine
>Affects Versions: v2.2.0
> Environment: HDP 2.5.6, Kylin 2.2.0
>Reporter: Vsevolod Ostapenko
>Assignee: Vsevolod Ostapenko
>Priority: Major
>  Labels: newbie
> Fix For: v2.3.0
>
> Attachments: KYLIN-3070.master.001.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Flat table storage format is currently hard-coded as SEQUENCEFILE in the 
> core-job/src/main/java/org/apache/kylin/job/JoinedFlatTable.java
> That prevents using Impala as a SQL engine while using beeline CLI (via 
> custom JDBC URL), as Impala cannot write sequence files.
> Adding a parameter to kylin.properties to override the default setting would 
> address the issue.
> Removing a hard-coded value for storage format might be good idea in and on 
> itself.



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

[jira] [Updated] (KYLIN-3073) Automatically refresh the 'Saved Queries' tab page when new query saved.

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3073:
-
Summary: Automatically refresh the 'Saved Queries' tab page when new query 
saved.   (was: When you save a new query condition, the 'Saved Queries' tab 
page will not be automatically refreshed.)

> Automatically refresh the 'Saved Queries' tab page when new query saved. 
> -
>
> Key: KYLIN-3073
> URL: https://issues.apache.org/jira/browse/KYLIN-3073
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3073-When-you-save-a-new-query-condition-the-S.patch, 
> add_a_new_record.png, init_status.png, manual_refresh.png, 
> saved_queries_not_refresh.png
>
>
> When you save a new query condition, the 'Saved Queries' tab will not be 
> automatically refreshed.
> 1. Open the 'Insight' page;
> 2. Choose the 'Saved Queries' tab page, you will see the current page is like 
> [^init_status.png];
> 3. Resubmit anyone query, then save it, just like [^add_a_new_record.png];
> 4. When you saved it, you will find the 'Saved Queries' tab page will not be 
> automatically refreshed, refer to [^saved_queries_not_refresh.png];
> 5. You should manually refresh it by clicking the 'Saved Queries' tab, refer 
> to [^manual_refresh.png].
> I check the code and find the reason, when closing the 'Save Query' dialog, 
> the code doesn't trigger refreshing 'Saved Queries' tab.
> I have repaired this code, please check the patch, thanks!



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

[jira] [Updated] (KYLIN-3074) Change cube access to project access in ExternalAclProvider.java

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3074:
-
Issue Type: Improvement  (was: Bug)

> Change cube access to project access in ExternalAclProvider.java
> 
>
> Key: KYLIN-3074
> URL: https://issues.apache.org/jira/browse/KYLIN-3074
> Project: Kylin
>  Issue Type: Improvement
>Affects Versions: v2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: 0001-KYLIN-3074-branch-2.2.x.patch, 
> 0001-KYLIN-3074-master.patch
>
>
> According to ranger recommendations, the following aspects were modified:
> 1.Cube ACL is removed since v2.2.0, we shuold modify the aclPermission name, 
> no longer cube access.
> 2.Remove unnecessary requests. For example, get cube and model access 
> entities, it will be recorded in the ranger audit log.
> 3.Remove unnecessary permission verification. Kylin currently used four 
> permissions(ADMINISTRATION,MANAGEMENT,OPERATION,READ), other permissions do 
> not need to be verified. Every time permission verification will be recorded 
> in the ranger audit log.



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

[jira] [Updated] (KYLIN-3073) When you save a new query condition, the 'Saved Queries' tab page will not be automatically refreshed.

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3073:
-
Priority: Minor  (was: Major)

> When you save a new query condition, the 'Saved Queries' tab page will not be 
> automatically refreshed.
> --
>
> Key: KYLIN-3073
> URL: https://issues.apache.org/jira/browse/KYLIN-3073
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3073-When-you-save-a-new-query-condition-the-S.patch, 
> add_a_new_record.png, init_status.png, manual_refresh.png, 
> saved_queries_not_refresh.png
>
>
> When you save a new query condition, the 'Saved Queries' tab will not be 
> automatically refreshed.
> 1. Open the 'Insight' page;
> 2. Choose the 'Saved Queries' tab page, you will see the current page is like 
> [^init_status.png];
> 3. Resubmit anyone query, then save it, just like [^add_a_new_record.png];
> 4. When you saved it, you will find the 'Saved Queries' tab page will not be 
> automatically refreshed, refer to [^saved_queries_not_refresh.png];
> 5. You should manually refresh it by clicking the 'Saved Queries' tab, refer 
> to [^manual_refresh.png].
> I check the code and find the reason, when closing the 'Save Query' dialog, 
> the code doesn't trigger refreshing 'Saved Queries' tab.
> I have repaired this code, please check the patch, thanks!



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

[jira] [Updated] (KYLIN-3073) When you save a new query condition, the 'Saved Queries' tab page will not be automatically refreshed.

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3073:
-
Issue Type: Improvement  (was: Bug)

> When you save a new query condition, the 'Saved Queries' tab page will not be 
> automatically refreshed.
> --
>
> Key: KYLIN-3073
> URL: https://issues.apache.org/jira/browse/KYLIN-3073
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3073-When-you-save-a-new-query-condition-the-S.patch, 
> add_a_new_record.png, init_status.png, manual_refresh.png, 
> saved_queries_not_refresh.png
>
>
> When you save a new query condition, the 'Saved Queries' tab will not be 
> automatically refreshed.
> 1. Open the 'Insight' page;
> 2. Choose the 'Saved Queries' tab page, you will see the current page is like 
> [^init_status.png];
> 3. Resubmit anyone query, then save it, just like [^add_a_new_record.png];
> 4. When you saved it, you will find the 'Saved Queries' tab page will not be 
> automatically refreshed, refer to [^saved_queries_not_refresh.png];
> 5. You should manually refresh it by clicking the 'Saved Queries' tab, refer 
> to [^manual_refresh.png].
> I check the code and find the reason, when closing the 'Save Query' dialog, 
> the code doesn't trigger refreshing 'Saved Queries' tab.
> I have repaired this code, please check the patch, thanks!



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

[jira] [Updated] (KYLIN-3076) Make kylin remember the choices we have made in the "Monitor>Jobs" page

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3076:
-
Priority: Minor  (was: Major)

> Make kylin remember the choices we have made in the "Monitor>Jobs" page
> ---
>
> Key: KYLIN-3076
> URL: https://issues.apache.org/jira/browse/KYLIN-3076
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3076-Make-kylin-remember-the-choices-we-have-m.patch
>
>
> In "Monitor>Jobs" page, the defaut setting is to list all the jobs in the 
> last one week, if we only want to see the jobs whose cube named "cube1" and 
> was successfully finished in the last one month, we have to type "cube1" in 
> the filter box, select "LAST ONE MONTH" in the drop-down box, and check the 
> "FINISHED" item in the job status checkbox, then click the "refresh" button, 
> the results we want will come out. But, when we leave this page for a moment, 
> for example, we click "MODEL" menu to see the model infomation and then click 
> "MONITOR" menu to turn back to the monitor page, we will find that all the 
> choices we have made was gone, and have to do it again to filter out the jobs 
> we want.
> We hope that kylin can remember the choices we have made in the 
> "Monitor>Jobs" page, so we don't have to make the same choices everytime when 
> we enter this page.



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

[jira] [Updated] (KYLIN-3078) Optimize the estimated size of percentile measure

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3078:
-
Summary: Optimize the estimated size of percentile measure  (was: the 
estimated size of percentile measure  is too big)

> Optimize the estimated size of percentile measure
> -
>
> Key: KYLIN-3078
> URL: https://issues.apache.org/jira/browse/KYLIN-3078
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Yifei Wu
>Assignee: Yifei Wu
>Priority: Major
> Fix For: v2.3.0
>
>
> To set a shard number that will be for controlling the size per shard 
> properly, we need to estimate cube size through accumulating all dimension 
> and measure size roughly before building a cube. But the way of calculating 
> the percentile measure is inaccurate currently and cause too many partitions 
> for cube storage. Furthermore, it may affect the performance of SQL query.



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

[jira] [Updated] (KYLIN-3078) the estimated size of percentile measure is too big

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3078:
-
Issue Type: Improvement  (was: Bug)

> the estimated size of percentile measure  is too big
> 
>
> Key: KYLIN-3078
> URL: https://issues.apache.org/jira/browse/KYLIN-3078
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Yifei Wu
>Assignee: Yifei Wu
>Priority: Major
> Fix For: v2.3.0
>
>
> To set a shard number that will be for controlling the size per shard 
> properly, we need to estimate cube size through accumulating all dimension 
> and measure size roughly before building a cube. But the way of calculating 
> the percentile measure is inaccurate currently and cause too many partitions 
> for cube storage. Furthermore, it may affect the performance of SQL query.



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

[jira] [Updated] (KYLIN-3080) Kylin Qlik Sense Integration Documentation

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3080:
-
Priority: Major  (was: Minor)

> Kylin Qlik Sense Integration Documentation
> --
>
> Key: KYLIN-3080
> URL: https://issues.apache.org/jira/browse/KYLIN-3080
> Project: Kylin
>  Issue Type: Task
>  Components: Documentation
>Reporter: Joanna He
>Assignee: Joanna He
>Priority: Major
>  Labels: documentation, newbie, patch
> Fix For: v2.3.0
>
> Attachments: 0001-connect_qilk.patch, Qlik-format-update.patch
>
>
> I have explored how Qlik sense can connect to Apache Kylin and found out Qlik 
> sense can be seamless integrated with Apache Kylin using its Direct Query 
> mode. 
> I have created a patch for the new document regarding kylin Qlik integration.



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

[jira] [Updated] (KYLIN-3086) Ignore the intermediate tables when loading Hive source tables

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3086:
-
Summary: Ignore the intermediate tables when loading Hive source tables  
(was: When you load Hive table metadata from server, the intermediate tables 
should not be loaded.)

> Ignore the intermediate tables when loading Hive source tables
> --
>
> Key: KYLIN-3086
> URL: https://issues.apache.org/jira/browse/KYLIN-3086
> Project: Kylin
>  Issue Type: Improvement
>  Components: General
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3086-When-you-load-Hive-table-metadata-from-se.patch, 
> contain_intermediate_tables.png
>
>
> 1. Load Hive table metadata from tree in 'Data Source' tab;
> 2. Choose one database, you will find the intermediate tables are also 
> loaded, refer to [^contain_intermediate_tables.png]
> I think intermediate tables are the inner tables, which should not be showed 
> to client, so I filter them in the server, please check the patch, thanks!



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

[jira] [Updated] (KYLIN-3087) Fix the DistributedLock release bug in GlobalDictionaryBuilder

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3087:
-
Summary: Fix the DistributedLock release bug in GlobalDictionaryBuilder  
(was: DistributedLock in GlobalDictionaryBuilder may not release)

> Fix the DistributedLock release bug in GlobalDictionaryBuilder
> --
>
> Key: KYLIN-3087
> URL: https://issues.apache.org/jira/browse/KYLIN-3087
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
>Reporter: Fangyuan Deng
>Assignee: Fangyuan Deng
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3087.1.patch, KYLIN-3087.patch
>
>
> In GlobalDictionaryBuilder.init(),
> this.builder = new AppendTrieDictionaryBuilder(baseDir, maxEntriesPerSlice, 
> true);
> if this line has exception, the DistributedLock will not release, and other 
> jobs can not run.
> so,I added a try catch.
> try {
> this.builder = new AppendTrieDictionaryBuilder(baseDir, 
> maxEntriesPerSlice, true);
> } catch (Throwable e) {
> lock.unlock(getLockPath(sourceColumn));
> throw new RuntimeException(String.format("Failed to create global 
> dictionary on %s ", sourceColumn), e);
> }



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

[jira] [Updated] (KYLIN-3098) Enable kylin.query.max-return-rows to limit the maximum row count returned to user

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3098:
-
Summary: Enable kylin.query.max-return-rows to limit the maximum row count 
returned to user  (was: add a new config kylin.query.max-return-rows for the 
maximum row count returned to user)

> Enable kylin.query.max-return-rows to limit the maximum row count returned to 
> user
> --
>
> Key: KYLIN-3098
> URL: https://issues.apache.org/jira/browse/KYLIN-3098
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-3098.patch
>
>




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

[jira] [Commented] (KYLIN-3098) add a new config kylin.query.max-return-rows for the maximum row count returned to user

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339111#comment-16339111
 ] 

Billy Liu commented on KYLIN-3098:
--

New config item 'kylin.query.max-return-rows' is introduced. The default value 
is 500

> add a new config kylin.query.max-return-rows for the maximum row count 
> returned to user
> ---
>
> Key: KYLIN-3098
> URL: https://issues.apache.org/jira/browse/KYLIN-3098
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: APACHE-KYLIN-3098.patch
>
>




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

[jira] [Updated] (KYLIN-3101) The "search" icon will separate from the "Filter" textbox when click the "showSteps" button of a job in the jobList

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3101:
-
Priority: Minor  (was: Major)

> The "search" icon will separate from the "Filter" textbox when click the 
> "showSteps" button of a job in the jobList
> ---
>
> Key: KYLIN-3101
> URL: https://issues.apache.org/jira/browse/KYLIN-3101
> Project: Kylin
>  Issue Type: Bug
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3101-The-search-icon-will-separate-from-the-Fi.patch, 
> search_icon_separate_from_the_filter_textbox.PNG
>
>
> In "Monitor>Jobs" page, when click the "showSteps" button of a job in the 
> jobList, the "search" icon will separate from the "Filter" textbox. And when 
> you resize the browser, it may also happen.



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

[jira] [Updated] (KYLIN-3102) Solve the problems for incomplete display of Hive Table tree.

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3102:
-
Summary: Solve the problems for incomplete display of Hive Table tree.  
(was: Solve the problems for incomplete display of tree.)

> Solve the problems for incomplete display of Hive Table tree.
> -
>
> Key: KYLIN-3102
> URL: https://issues.apache.org/jira/browse/KYLIN-3102
> Project: Kylin
>  Issue Type: Bug
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3102-Solve-the-problems-for-incomplete-display.patch, MG148.jpeg, 
> incomplete_display1.png, incomplete_display2.png, screenshot-1.png
>
>
> When you zoom out the web page, and expand the tree, you will find the tree 
> is displayed incompletely, just like [^incomplete_display1.png] and 
> [^incomplete_display2.png].
> Then I have repaired them, please check the patch, thanks!



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

[jira] [Updated] (KYLIN-3106) DefaultScheduler.shutdown should use ExecutorService.shutdownNow instead of ExecutorService.shutdown

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3106:
-
Priority: Minor  (was: Major)

> DefaultScheduler.shutdown should use ExecutorService.shutdownNow instead of 
> ExecutorService.shutdown
> 
>
> Key: KYLIN-3106
> URL: https://issues.apache.org/jira/browse/KYLIN-3106
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Reporter: hongbin ma
>Assignee: hongbin ma
>Priority: Minor
> Fix For: v2.3.0
>
>
> java.util.concurrent.ExecutorService#shutdownNow will interrupt running 
> worker threads, while java.util.concurrent.ExecutorService#shutdown will not.
> if interrupt signal is sent, a worker thread can get aware of it and abort 
> itself in time. 



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

[jira] [Updated] (KYLIN-3110) The dashboard page has some display problems.

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3110:
-
Priority: Minor  (was: Major)

> The dashboard page has some display problems.
> -
>
> Key: KYLIN-3110
> URL: https://issues.apache.org/jira/browse/KYLIN-3110
> Project: Kylin
>  Issue Type: Bug
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3110-The-dashboard-page-has-some-display-probl.patch, 
> incomplete_display_and_message_not_right.png
>
>
> The dashboard page has some display problems.
> 1. The 'Monthly' and 'Weekly' display incompletely;
> 2. The 'showValue' should be 'Show Value'.
> refer to [^incomplete_display_and_message_not_right.png]



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

[jira] [Updated] (KYLIN-3111) Close of HBaseAdmin instance should be placed in finally block

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3111:
-
Summary: Close of HBaseAdmin instance should be placed in finally block  
(was: Close of Admin instance should be placed in finally block)

> Close of HBaseAdmin instance should be placed in finally block
> --
>
> Key: KYLIN-3111
> URL: https://issues.apache.org/jira/browse/KYLIN-3111
> Project: Kylin
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Chao Long
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: 
> KYLIN-3111-Place-close-of-admin-instance-into-finally-block.patch
>
>
> Looking at the code in DeployCoprocessorCLI.java and 
> HtableAlterMetadataCLI.java , I see that close of Admin instance is without 
> finally block:
> {code}
> hbaseAdmin.disableTable(table.getTableName());
> table.setValue(metadataKey, metadataValue);
> hbaseAdmin.modifyTable(table.getTableName(), table);
> hbaseAdmin.enableTable(table.getTableName());
> hbaseAdmin.close();
> {code}
> If any exception is thrown in the operations prior to the close(), the 
> close() would be skipped, leading to resource leak.



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

[jira] [Updated] (KYLIN-3112) The job 'Pause' operation has logic bug in the kylin server.

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3112:
-
Priority: Minor  (was: Major)

> The job 'Pause' operation has logic bug in the kylin server.
> 
>
> Key: KYLIN-3112
> URL: https://issues.apache.org/jira/browse/KYLIN-3112
> Project: Kylin
>  Issue Type: Bug
>  Components: General
>Affects Versions: v2.2.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3112-The-job-Pause-operation-has-logic-bug-in-.patch, 
> job_click_pause.png, job_click_pause_again.png
>
>
> 1. Click the 'Pause' item, although the result is successful, when you expand 
> the action, you will also find the 'Pause' item. refer to 
> [^job_click_pause.png]
> 2. When you click  'Pause' item again( the second click), when the result is 
> successful, then you expand the action, you will find the 'Pause' item has 
> changed to 'Resume'. refer to [^job_click_pause_again.png]
> I checked the logic code of job pause in kylin server, I found the job status 
> changed to new status in the metadata storage, but not changed in JobInstance 
> which would be sent to client, so the client got the old job status.
> Then you clicked 'Pause' item again, the JobInstance would be fetched from 
> the metadata storage, so it was the new one, then the client woud get the new 
> job status. 
> So I fixed it, please check the patch, thanks!



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

[jira] [Updated] (KYLIN-3114) Make timeout for the queries submitted through the Web UI configurable

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3114:
-
Issue Type: Improvement  (was: Bug)

> Make timeout for the queries submitted through the Web UI configurable
> --
>
> Key: KYLIN-3114
> URL: https://issues.apache.org/jira/browse/KYLIN-3114
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.2.0
> Environment: HDP 2.5.6, Kylin 2.2.0
>Reporter: Vsevolod Ostapenko
>Assignee: Vsevolod Ostapenko
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: KYLIN-3114.master.002.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Currently query.js hard codes timeout for the queries submitted via Web UI to 
> be 300_000 milliseconds.
> Depending on the situation, the default value can be either too large, or too 
> small, especially when query does not hit any cube and is passed through to 
> Hive or Impala.
> Query timeout should be made configurable via kylin.properties.



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

[jira] [Updated] (KYLIN-3124) Support horizontal scroll bar in 'Insight'

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3124:
-
Summary: Support horizontal scroll bar in 'Insight'  (was: Difficulty in 
viewing long cube names due to missing horizontal scroll bar in browser)

> Support horizontal scroll bar in 'Insight'
> --
>
> Key: KYLIN-3124
> URL: https://issues.apache.org/jira/browse/KYLIN-3124
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.2.0
> Environment: Windows , Chrome Version 63.0.3239.108,Firefox 57.0.2 
>Reporter: atul
>Assignee: Zhixiong Chen
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: horizontal_scrollbar_missing.jpg
>
>
> As attached in screenshot, ,due to missing scrollbar in Kylin Web UI  
> (http://:7070/kylin/query) , it's difficult to view full name of cube 
> after executing query from "Insight" view of UI.



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

[jira] [Updated] (KYLIN-3124) Difficulty in viewing long cube names due to missing horizontal scroll bar in browser

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3124:
-
Issue Type: Improvement  (was: Bug)

> Difficulty in viewing long cube names due to missing horizontal scroll bar in 
> browser
> -
>
> Key: KYLIN-3124
> URL: https://issues.apache.org/jira/browse/KYLIN-3124
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.2.0
> Environment: Windows , Chrome Version 63.0.3239.108,Firefox 57.0.2 
>Reporter: atul
>Assignee: Zhixiong Chen
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: horizontal_scrollbar_missing.jpg
>
>
> As attached in screenshot, ,due to missing scrollbar in Kylin Web UI  
> (http://:7070/kylin/query) , it's difficult to view full name of cube 
> after executing query from "Insight" view of UI.



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

[jira] [Reopened] (KYLIN-3124) Difficulty in viewing long cube names due to missing horizontal scroll bar in browser

[Billy Liu (JIRA)]

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

Billy Liu reopened KYLIN-3124:
--

> Difficulty in viewing long cube names due to missing horizontal scroll bar in 
> browser
> -
>
> Key: KYLIN-3124
> URL: https://issues.apache.org/jira/browse/KYLIN-3124
> Project: Kylin
>  Issue Type: Bug
>  Components: Web 
>Affects Versions: v2.2.0
> Environment: Windows , Chrome Version 63.0.3239.108,Firefox 57.0.2 
>Reporter: atul
>Assignee: Zhixiong Chen
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: horizontal_scrollbar_missing.jpg
>
>
> As attached in screenshot, ,due to missing scrollbar in Kylin Web UI  
> (http://:7070/kylin/query) , it's difficult to view full name of cube 
> after executing query from "Insight" view of UI.



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

[jira] [Comment Edited] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339104#comment-16339104
 ] 

Billy Liu edited comment on KYLIN-3125 at 1/25/18 11:30 AM:


# Absolute path to beeline shell, can be set to spark beeline instead of the 
default hive beeline on PATH
 kylin.source.hive.beeline-shell=beeline

# given SparkSQL connects to the same Hive metastore.
 kylin.source.hive.enable-sparksql-for-table-ops=true
 kylin.source.hive.sparksql-beeline-shell=/path/to/spark-client/bin/beeline
 kylin.source.hive.sparksql-beeline-params=-n root- -hiveconf 
hive.security.authorization.sqlstd.confwhitelist.append='mapreduce.job.*|dfs.*' 
-u jdbc:hive2://localhost:1
  


was (Author: yimingliu):
# Absolute path to beeline shell, can be set to spark beeline instead of the 
default hive beeline on PATH
kylin.source.hive.beeline-shell=beeline
 
# given SparkSQL connects to the same Hive metastore.
kylin.source.hive.enable-sparksql-for-table-ops=true
kylin.source.hive.sparksql-beeline-shell=/path/to/spark-client/bin/beeline
kylin.source.hive.sparksql-beeline-params=-n root --hiveconf 
hive.security.authorization.sqlstd.confwhitelist.append='mapreduce.job.*|dfs.*' 
-u jdbc:hive2://localhost:1
 

> Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
> 
>
> Key: KYLIN-3125
> URL: https://issues.apache.org/jira/browse/KYLIN-3125
> Project: Kylin
>  Issue Type: New Feature
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> It is said that SparkSQL is much faster then Hive when used to create flat 
> table.



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

[jira] [Comment Edited] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339104#comment-16339104
 ] 

Billy Liu edited comment on KYLIN-3125 at 1/25/18 11:30 AM:


# Absolute path to beeline shell, can be set to spark beeline instead of the 
default hive beeline on PATH

kylin.source.hive.beeline-shell=beeline

# given SparkSQL connects to the same Hive metastore.

kylin.source.hive.enable-sparksql-for-table-ops=true
 kylin.source.hive.sparksql-beeline-shell=/path/to/spark-client/bin/beeline
 kylin.source.hive.sparksql-beeline-params=-n root- -hiveconf 
hive.security.authorization.sqlstd.confwhitelist.append='mapreduce.job.*|dfs.*' 
-u jdbc:hive2://localhost:1
  


was (Author: yimingliu):
# Absolute path to beeline shell, can be set to spark beeline instead of the 
default hive beeline on PATH
 kylin.source.hive.beeline-shell=beeline

# given SparkSQL connects to the same Hive metastore.
 kylin.source.hive.enable-sparksql-for-table-ops=true
 kylin.source.hive.sparksql-beeline-shell=/path/to/spark-client/bin/beeline
 kylin.source.hive.sparksql-beeline-params=-n root- -hiveconf 
hive.security.authorization.sqlstd.confwhitelist.append='mapreduce.job.*|dfs.*' 
-u jdbc:hive2://localhost:1
  

> Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
> 
>
> Key: KYLIN-3125
> URL: https://issues.apache.org/jira/browse/KYLIN-3125
> Project: Kylin
>  Issue Type: New Feature
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> It is said that SparkSQL is much faster then Hive when used to create flat 
> table.



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

[jira] [Issue Comment Deleted] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3125:
-
Comment: was deleted

(was: Commit: http://git-wip-us.apache.org/repos/asf/kylin/commit/acc9d0c8)

> Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
> 
>
> Key: KYLIN-3125
> URL: https://issues.apache.org/jira/browse/KYLIN-3125
> Project: Kylin
>  Issue Type: New Feature
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> It is said that SparkSQL is much faster then Hive when used to create flat 
> table.



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

[jira] [Commented] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339104#comment-16339104
 ] 

Billy Liu commented on KYLIN-3125:
--

# Absolute path to beeline shell, can be set to spark beeline instead of the 
default hive beeline on PATH
kylin.source.hive.beeline-shell=beeline
 
# given SparkSQL connects to the same Hive metastore.
kylin.source.hive.enable-sparksql-for-table-ops=true
kylin.source.hive.sparksql-beeline-shell=/path/to/spark-client/bin/beeline
kylin.source.hive.sparksql-beeline-params=-n root --hiveconf 
hive.security.authorization.sqlstd.confwhitelist.append='mapreduce.job.*|dfs.*' 
-u jdbc:hive2://localhost:1
 

> Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
> 
>
> Key: KYLIN-3125
> URL: https://issues.apache.org/jira/browse/KYLIN-3125
> Project: Kylin
>  Issue Type: New Feature
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> It is said that SparkSQL is much faster then Hive when used to create flat 
> table.



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

[jira] [Commented] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339103#comment-16339103
 ] 

Billy Liu commented on KYLIN-3125:
--

Commit: http://git-wip-us.apache.org/repos/asf/kylin/commit/acc9d0c8

> Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
> 
>
> Key: KYLIN-3125
> URL: https://issues.apache.org/jira/browse/KYLIN-3125
> Project: Kylin
>  Issue Type: New Feature
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> It is said that SparkSQL is much faster then Hive when used to create flat 
> table.



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

[jira] [Commented] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"

[Billy Liu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339102#comment-16339102
 ] 

Billy Liu commented on KYLIN-3125:
--

Commit: http://git-wip-us.apache.org/repos/asf/kylin/commit/acc9d0c8

> Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
> 
>
> Key: KYLIN-3125
> URL: https://issues.apache.org/jira/browse/KYLIN-3125
> Project: Kylin
>  Issue Type: New Feature
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> It is said that SparkSQL is much faster then Hive when used to create flat 
> table.



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

[jira] [Updated] (KYLIN-3125) Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3125:
-
Issue Type: New Feature  (was: Improvement)

> Support SparkSql in Cube building step "Create Intermediate Flat Hive Table"
> 
>
> Key: KYLIN-3125
> URL: https://issues.apache.org/jira/browse/KYLIN-3125
> Project: Kylin
>  Issue Type: New Feature
>Reporter: liyang
>Assignee: liyang
>Priority: Major
> Fix For: v2.3.0
>
>
> It is said that SparkSQL is much faster then Hive when used to create flat 
> table.



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

[jira] [Updated] (KYLIN-3135) Fix regular expression bug in SQL comments

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3135:
-
Summary: Fix regular expression bug in SQL comments  (was: regular 
expression of multi line comment pattern was wrong)

> Fix regular expression bug in SQL comments
> --
>
> Key: KYLIN-3135
> URL: https://issues.apache.org/jira/browse/KYLIN-3135
> Project: Kylin
>  Issue Type: Bug
>Reporter: hahaya
>Assignee: hahaya
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: 0001-KYLIN-3135.patch
>
>
> Hi,all.
> Recently,I was testing query function of kylin,
> sometimes I just comment with /**/ instead of delete the sql,cause I need to 
> query and compare again.
> And I was confused that the results says it was "No Support Sql",but it can 
> query success without comments.
> For example,
> {code:java}
> /*
> select count(*) from kylin_sales;
> */
> select * from kylin_sales;
> {code}
> So I view the code and find the commentPatterns of  /\**/  was 
> {code:java}
> /\\*[^\\*/]*
> {code}
> ,clearly it was wrong.
> The regular expression of [abc] means any character in abc,such as a or b.
> So the [^\\*/] means that * or / can't appear,
> But under this circumstances the */ need to be as a string not separated 
> character.
> the */ can't appear not * or / can't appear.
> I rewrite the regular expression,
> {code:java}
> /\\*[\\s\\S]*?\\*/
> {code}
> if you think it's necessary to change the old code,please review and replace 
> it.
> Thank for you time.



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

[jira] [Updated] (KYLIN-3150) Support different compression in PercentileCounter measure

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3150:
-
Summary: Support different compression in PercentileCounter measure  (was: 
PercentileCounter maxlength is too small)

> Support different compression in PercentileCounter measure
> --
>
> Key: KYLIN-3150
> URL: https://issues.apache.org/jira/browse/KYLIN-3150
> Project: Kylin
>  Issue Type: Improvement
>  Components: Query Engine
>Affects Versions: v2.2.0
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Major
> Fix For: v2.3.0
>
>
> With Percentile 1000, the count size more than 10 * 1024. We should use 
> different max length with different compression.



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

[jira] [Updated] (KYLIN-3150) PercentileCounter maxlength is too small

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3150:
-
Issue Type: Improvement  (was: Bug)

> PercentileCounter maxlength is too small
> 
>
> Key: KYLIN-3150
> URL: https://issues.apache.org/jira/browse/KYLIN-3150
> Project: Kylin
>  Issue Type: Improvement
>  Components: Query Engine
>Affects Versions: v2.2.0
>Reporter: yiming.xu
>Assignee: yiming.xu
>Priority: Major
> Fix For: v2.3.0
>
>
> With Percentile 1000, the count size more than 10 * 1024. We should use 
> different max length with different compression.



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

[jira] [Updated] (KYLIN-3151) Query History should allow to have the same sql in different project

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3151:
-
Issue Type: Improvement  (was: Bug)

> Query History should allow to have the same sql in different project
> 
>
> Key: KYLIN-3151
> URL: https://issues.apache.org/jira/browse/KYLIN-3151
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Reporter: peng.jianhua
>Assignee: Zhixiong Chen
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3151-Query-History-should-allow-to-have-the-sa.patch, 01.PNG
>
>
> Now if I query the sql 'select trans_id from kylin_sales' in project p1,the 
> Query History tab will have the history,please refer to 01.png.
> And then I query the same sql in project p2,we can't find the query history 
> of project  p2.
> In my opinion,the query history should be distinguished by project too, not 
> only sql itself.



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

[jira] [Updated] (KYLIN-3157) Enhance query timeout to entire query life cycle

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3157:
-
Summary: Enhance query timeout to entire query life cycle  (was: Enhance 
Kylin' s timeout)

> Enhance query timeout to entire query life cycle
> 
>
> Key: KYLIN-3157
> URL: https://issues.apache.org/jira/browse/KYLIN-3157
> Project: Kylin
>  Issue Type: Improvement
>Reporter: jiatao.tao
>Assignee: jiatao.tao
>Priority: Major
> Fix For: v2.3.0
>
>
> Nowadays, kylin's query timeout( kylin.query.timeout-seconds ) is only for 
> one OLAP context, should be for the entire query life cycle.



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

[jira] [Updated] (KYLIN-3157) Enhance Kylin' s timeout

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3157:
-
Priority: Major  (was: Minor)

> Enhance Kylin' s timeout
> 
>
> Key: KYLIN-3157
> URL: https://issues.apache.org/jira/browse/KYLIN-3157
> Project: Kylin
>  Issue Type: Improvement
>Reporter: jiatao.tao
>Assignee: jiatao.tao
>Priority: Major
> Fix For: v2.3.0
>
>
> Nowadays, kylin's query timeout( kylin.query.timeout-seconds ) is only for 
> one OLAP context, should be for the entire query life cycle.



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

[jira] [Updated] (KYLIN-3164) HBase connection must be closed when clearing connection pool

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3164:
-
Priority: Minor  (was: Major)

> HBase connection must be closed when clearing connection pool
> -
>
> Key: KYLIN-3164
> URL: https://issues.apache.org/jira/browse/KYLIN-3164
> Project: Kylin
>  Issue Type: Bug
>Reporter: liyang
>Assignee: liyang
>Priority: Minor
> Fix For: v2.3.0
>
>
> Currently {{HBaseConnection.clearConnCache()}} does not invoke {{close()}} on 
> hbase connections. But it should.



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

[jira] [Updated] (KYLIN-3159) Remove unnecessary cube access request

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3159:
-
Issue Type: Improvement  (was: Bug)

> Remove unnecessary cube access request
> --
>
> Key: KYLIN-3159
> URL: https://issues.apache.org/jira/browse/KYLIN-3159
> Project: Kylin
>  Issue Type: Improvement
>  Components: Web 
>Affects Versions: v2.3.0
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
> Fix For: v2.3.0
>
> Attachments: 
> 0001-KYLIN-3159-Remove-unnecessary-cube-access-request.patch
>
>




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

[jira] [Updated] (KYLIN-3165) Fix the IllegalCannot auto mege segments

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3165:
-
Summary: Fix the IllegalCannot auto mege segments  (was: Cannot auto mege 
segments)

> Fix the IllegalCannot auto mege segments
> 
>
> Key: KYLIN-3165
> URL: https://issues.apache.org/jira/browse/KYLIN-3165
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
>Reporter: Yang Hao
>Assignee: Yang Hao
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3165.apache-master.001.patch
>
>
> The function of auto merge loses efficacy after we upgrade to 2.2.0, related 
> stack is:
> 2018-01-14 11:21:10,965 ERROR [Thread-694] service.CacheService:88 : Error in 
> updateOnNewSegmentReady()
> java.lang.IllegalArgumentException
>  at com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
>  at org.apache.kylin.cube.CubeManager.mergeSegments(CubeManager.java:547)
>  at 
> org.apache.kylin.rest.service.CubeService.mergeCubeSegment(CubeService.java:646)
>  at 
> org.apache.kylin.rest.service.CubeService.updateOnNewSegmentReady(CubeService.java:594)
>  at 
> org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke()
>  at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)
>  at 
> org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$eaadc7fa.updateOnNewSegmentReady()
>  at org.apache.kylin.rest.service.CacheService$1$1.run(CacheService.java:86)



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

[jira] [Updated] (KYLIN-3165) Fix the IllegalArgumentException during segments auto merge

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3165:
-
Summary: Fix the IllegalArgumentException during segments auto merge  (was: 
Fix the IllegalCannot auto mege segments)

> Fix the IllegalArgumentException during segments auto merge
> ---
>
> Key: KYLIN-3165
> URL: https://issues.apache.org/jira/browse/KYLIN-3165
> Project: Kylin
>  Issue Type: Bug
>  Components: Job Engine
>Affects Versions: v2.2.0
>Reporter: Yang Hao
>Assignee: Yang Hao
>Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-3165.apache-master.001.patch
>
>
> The function of auto merge loses efficacy after we upgrade to 2.2.0, related 
> stack is:
> 2018-01-14 11:21:10,965 ERROR [Thread-694] service.CacheService:88 : Error in 
> updateOnNewSegmentReady()
> java.lang.IllegalArgumentException
>  at com.google.common.base.Preconditions.checkArgument(Preconditions.java:76)
>  at org.apache.kylin.cube.CubeManager.mergeSegments(CubeManager.java:547)
>  at 
> org.apache.kylin.rest.service.CubeService.mergeCubeSegment(CubeService.java:646)
>  at 
> org.apache.kylin.rest.service.CubeService.updateOnNewSegmentReady(CubeService.java:594)
>  at 
> org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke()
>  at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
>  at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)
>  at 
> org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$eaadc7fa.updateOnNewSegmentReady()
>  at org.apache.kylin.rest.service.CacheService$1$1.run(CacheService.java:86)



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

[jira] [Updated] (KYLIN-3173) DefaultScheduler shutdown didn't reset field initialized.

[Billy Liu (JIRA)]

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

Billy Liu updated KYLIN-3173:
-
Priority: Minor  (was: Major)

> DefaultScheduler shutdown didn't reset field initialized.
> -
>
> Key: KYLIN-3173
> URL: https://issues.apache.org/jira/browse/KYLIN-3173
> Project: Kylin
>  Issue Type: Bug
>Reporter: jiatao.tao
>Assignee: jiatao.tao
>Priority: Minor
> Fix For: v2.3.0
>
>




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