[jira] [Commented] (KYLIN-3311) Segments overlap error (refactor write conflict exception)

2018-04-02 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on KYLIN-3311:


Commit 3222de27c508ed3e7576330dc8c40206fe6cd84d in kylin's branch 
refs/heads/sync from Li Yang
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=3222de2 ]

KYLIN-3311 refactor Resource.checkAndPutResourceImpl() to throw 
WriteConflictException


> Segments overlap error (refactor write conflict exception)
> --
>
> Key: KYLIN-3311
> URL: https://issues.apache.org/jira/browse/KYLIN-3311
> Project: Kylin
>  Issue Type: Bug
>  Components: Metadata
>Affects Versions: v2.3.0
>Reporter: xujing
>Priority: Major
>  Labels: build
> Attachments: Segments_Overlap_ErrorLog.txt
>
>
> when "updateCubeWithRetry" method be called at first time ,
> line newSegs.validate();was passed .
> then 
> cube = crud.save(cube);seem with error throw exception
> write conflict to update cube  at try 0 ,will retry...
> while retry "updateCubeWithRetry" start
> line newSegs.validate();was not passed .
> throw exception 
> Segments overlap: [2018031800_2018031900] and 
> sales_order_channel[2018031800_201803
> 1900]



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

[jira] [Commented] (KYLIN-3324) NegativeArraySizeException in CreateDictionaryJob$2.getDictionary()

2018-04-02 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on KYLIN-3324:


Commit 35009d465b9c628e2be8ab9bceff7852e20a4d42 in kylin's branch 
refs/heads/sync from Li Yang
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=35009d4 ]

KYLIN-3324 fix NegativeArraySizeException in 
CreateDictionaryJob$2.getDictionary()


> NegativeArraySizeException in CreateDictionaryJob$2.getDictionary()
> ---
>
> Key: KYLIN-3324
> URL: https://issues.apache.org/jira/browse/KYLIN-3324
> Project: Kylin
>  Issue Type: Bug
>Reporter: liyang
>Assignee: liyang
>Priority: Major
>
> During cube build, got following exception:
> {noformat}
> 2018-01-31 09:58:14,982 ERROR [Scheduler 311988476 Job 
> b931b081-3b44-462b-9bce-e15bf245f1b9-862] common.HadoopShellExecutable : 
> error execute 
> HadoopShellExecutable{id=b931b081-3b44-462b-9bce-e15bf245f1b9-03, name=Build 
> Dimension Dictionary, state=RUNNING}
> java.lang.NegativeArraySizeException
>   at 
> org.apache.hadoop.io.BytesWritable.setCapacity(BytesWritable.java:144)
>   at org.apache.hadoop.io.BytesWritable.setSize(BytesWritable.java:123)
>   at org.apache.hadoop.io.BytesWritable.readFields(BytesWritable.java:179)
>   at 
> org.apache.hadoop.io.SequenceFile$Reader.getCurrentValue(SequenceFile.java:2259)
>   at org.apache.hadoop.io.SequenceFile$Reader.next(SequenceFile.java:2387)
>   at 
> org.apache.kylin.engine.mr.steps.CreateDictionaryJob$2.getDictionary(CreateDictionaryJob.java:87)
>   at 
> org.apache.kylin.cube.cli.DictionaryGeneratorCLI.processSegment(DictionaryGeneratorCLI.java:62)
>   at 
> org.apache.kylin.cube.cli.DictionaryGeneratorCLI.processSegment(DictionaryGeneratorCLI.java:49)
>   at 
> org.apache.kylin.engine.mr.steps.CreateDictionaryJob.run(CreateDictionaryJob.java:66)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
>   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
>   at 
> org.apache.kylin.engine.mr.common.HadoopShellExecutable.doWork(HadoopShellExecutable.java:62)
>   at 
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:125)
>   at 
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:64)
>   at 
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:125)
>   at 
> org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:156)
>   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){noformat}
> Root cause seems to be 
> https://stackoverflow.com/questions/24127304/negativearraysizeexception-when-creating-a-sequencefile-with-large-1gb-bytesw



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

[jira] [Commented] (KYLIN-3315) allow each project to set its own source in project level override configuration

2018-04-02 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on KYLIN-3315:


Commit f48984b58067f00bfdf3ccf5c15bcfbe63c30775 in kylin's branch 
refs/heads/sync from [~lidong_sjtu]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f48984b ]

KYLIN-3315 allow each project to set its own source


> allow each project to set its own source in project level override 
> configuration
> 
>
> Key: KYLIN-3315
> URL: https://issues.apache.org/jira/browse/KYLIN-3315
> Project: Kylin
>  Issue Type: Improvement
>  Components: Metadata
>Reporter: Dong Li
>Priority: Major
>
> Currently, all projects connect to the same source which is set in 
> kylin.properties with kylin.source.default property.
> It's better to allow each project to set its own source in project level 
> override configuration.
> As the result, we can have project A connects to JDBC, and project B connects 
> to Hive.



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

[jira] [Commented] (KYLIN-3277) Kylin should override hiveconf settings when connecting to hive using jdbc

2018-04-02 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on KYLIN-3277:


Commit 2e58857d8d6903e5a0e5dc92efdaf93e7fe1f479 in kylin's branch 
refs/heads/sync from [~nichunen]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=2e58857 ]

KYLIN-3277 Code review


> Kylin should override hiveconf settings when connecting to hive using jdbc
> --
>
> Key: KYLIN-3277
> URL: https://issues.apache.org/jira/browse/KYLIN-3277
> Project: Kylin
>  Issue Type: Bug
>Reporter: Chuqian Yu
>Assignee: Chuqian Yu
>Priority: Major
>  Labels: patch
> Fix For: v2.4.0
>
> Attachments: 0001-KYLIN-3277.patch
>
>
> Hi, kylin developers. My cube building procedure failing at Step 2 
> "Redistribute Flat Hive Table" because Kylin always trying to submit a mr job 
> to the default yarn queue.
>  
> I have overrided the mapred.job.queue.name property in both 
> kylin_hive_conf.xml and kylin.properties but it doesn't work. 
>  
> kylin.properties
> ```
> kylin.source.hive.beeline-params=-n hive -p hive --hiveconf 
> mapred.job.queue.name=myQueue  -u 
> "jdbc:hive2://myZk:2181/;serviceDiscoveryMode=zooKeeper;" 
> ```
>  
> kylin_hive_conf.xml
> ```
>    
>    mapred.job.queue.name
>    myQueue
>    
> ```
>  
> After digging into the source code ,I found that kylin try to get the row 
> count of hive table before redistributing it. But it dose not override the 
> hive configuration when using jdbc to connect to hive server.
>  
>  
>  



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

[jira] [Commented] (KYLIN-3315) allow each project to set its own source in project level override configuration

2018-04-02 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on KYLIN-3315:


Commit 54bdae63cfca137c02cdf8749f93d152a9ac2010 in kylin's branch 
refs/heads/sync from [~lidong_sjtu]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=54bdae6 ]

KYLIN-3315 allow each project to set its own source


> allow each project to set its own source in project level override 
> configuration
> 
>
> Key: KYLIN-3315
> URL: https://issues.apache.org/jira/browse/KYLIN-3315
> Project: Kylin
>  Issue Type: Improvement
>  Components: Metadata
>Reporter: Dong Li
>Priority: Major
>
> Currently, all projects connect to the same source which is set in 
> kylin.properties with kylin.source.default property.
> It's better to allow each project to set its own source in project level 
> override configuration.
> As the result, we can have project A connects to JDBC, and project B connects 
> to Hive.



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

[jira] [Commented] (KYLIN-3277) Kylin should override hiveconf settings when connecting to hive using jdbc

2018-04-02 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on KYLIN-3277:


Commit 25b4b3bc06b30a4030f4949d97a05566bcbddca4 in kylin's branch 
refs/heads/sync from [~yuchuqian]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=25b4b3b ]

KYLIN-3277 Kylin should override hiveconf settings when connecting to hive 
using jdbc

Signed-off-by: nichunen 


> Kylin should override hiveconf settings when connecting to hive using jdbc
> --
>
> Key: KYLIN-3277
> URL: https://issues.apache.org/jira/browse/KYLIN-3277
> Project: Kylin
>  Issue Type: Bug
>Reporter: Chuqian Yu
>Assignee: Chuqian Yu
>Priority: Major
>  Labels: patch
> Fix For: v2.4.0
>
> Attachments: 0001-KYLIN-3277.patch
>
>
> Hi, kylin developers. My cube building procedure failing at Step 2 
> "Redistribute Flat Hive Table" because Kylin always trying to submit a mr job 
> to the default yarn queue.
>  
> I have overrided the mapred.job.queue.name property in both 
> kylin_hive_conf.xml and kylin.properties but it doesn't work. 
>  
> kylin.properties
> ```
> kylin.source.hive.beeline-params=-n hive -p hive --hiveconf 
> mapred.job.queue.name=myQueue  -u 
> "jdbc:hive2://myZk:2181/;serviceDiscoveryMode=zooKeeper;" 
> ```
>  
> kylin_hive_conf.xml
> ```
>    
>    mapred.job.queue.name
>    myQueue
>    
> ```
>  
> After digging into the source code ,I found that kylin try to get the row 
> count of hive table before redistributing it. But it dose not override the 
> hive configuration when using jdbc to connect to hive server.
>  
>  
>  



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

[jira] [Commented] (KYLIN-2899) Enable segment level query cache

2018-04-02 Thread liyang (JIRA) 

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

liyang commented on KYLIN-2899:
---

Very good document! Thanks Ma Gang!

Very helpful for understanding.

> Enable segment level query cache
> 
>
> Key: KYLIN-2899
> URL: https://issues.apache.org/jira/browse/KYLIN-2899
> Project: Kylin
>  Issue Type: Sub-task
>  Components: Query Engine
>Affects Versions: v2.1.0
>Reporter: Zhong Yanghong
>Assignee: Ma Gang
>Priority: Major
>




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

[jira] [Commented] (KYLIN-3221) Some improvements for lookup table

2018-04-02 Thread liyang (JIRA) 

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

liyang commented on KYLIN-3221:
---

+1 Nice proposal. The global snapshot table can be one way to support slowly 
changing dimension tables.

> Some improvements for lookup table 
> ---
>
> Key: KYLIN-3221
> URL: https://issues.apache.org/jira/browse/KYLIN-3221
> Project: Kylin
>  Issue Type: Improvement
>  Components: Job Engine, Metadata, Query Engine
>Reporter: Ma Gang
>Assignee: Ma Gang
>Priority: Major
>
> There are two limitations for current look table design:
>  # lookup table size is limited, because table snapshot need to be cached in 
> Kylin server, too large snapshot table will break the server.
>  # lookup table snapshot references are stored in all segments of the cube, 
> cannot support global snapshot table, the global snapshot table means when 
> the lookup table is updated, it will take effective for all segments.
> To resolve the above limitations, we decide to do some improvements for the 
> existing lookup table design, below is the initial document, any comments and 
> suggestions are welcome.
> h2. Metadata
> Will add a new property in CubeDesc to describe how lookup tables will be 
> snapshot, it can be defined during the cube design
> |{{@JsonProperty}}{{(}}{{"snapshot_table_desc_list"}}{{)}}
>  {{private}} {{List snapshotTableDescList = 
> Collections.emptyList();}}|
>  SnapshotTableDesc defines how table is stored and whether it is global or 
> not, currently we can support two types of store:
>  # "metaStore",  table snapshot is stored in the metadata store, it is the 
> same as current design, and this is the default option.
>  # "hbaseStore', table snapshot is stored in an additional hbase table.
> |{{@JsonProperty}}{{(}}{{"table_name"}}{{)}}
>  {{private}} {{String tableName;}}
>   
>  {{@JsonProperty}}{{(}}{{"store_type"}}{{)}}
>  {{private}} {{String snapshotStorageType = }}{{"metaStore"}}{{;}}
>   
>  {{@JsonProperty}}{{(}}{{"global"}}{{)}}
>  {{private}} {{boolean}} {{global = }}{{false}}{{;}}|
>  
> Add 'snapshots' property in CubeInstance, to store snapshots resource path 
> for each table, when the table snapshot is set to global in cube design:
> |{{@JsonProperty}}{{(}}{{"snapshots"}}{{)}}
>  {{private}} {{Map snapshots; }}{{// tableName -> 
> tableResoucePath mapping}}|
>  
> Add new meta model ExtTableSnapshot to describe the extended table snapshot 
> information, the information is stored in a new metastore path: 
> /ext_table_snapshot/\{tableName}/\{uuid}.snapshot, the metadata including 
> following info:
> |{{@JsonProperty}}{{(}}{{"tableName"}}{{)}}
>  {{private}} {{String tableName;}}
>   
>  {{@JsonProperty}}{{(}}{{"signature"}}{{)}}
>  {{private}} {{TableSignature signature;}}
>   
>  {{@JsonProperty}}{{(}}{{"storage_location_identifier"}}{{)}}
>  {{private}} {{String storageLocationIdentifier;}}
>   
> @JsonProperty("key_columns")
>  private String[] keyColumns;  // the key columns of the table
>  
> @JsonProperty("storage_type")
>  private String storageType;
>  
>  {{@JsonProperty}}{{(}}{{"size"}}{{)}}
>  {{private}} {{long}} {{size;}}
>   
>  {{@JsonProperty}}{{(}}{{"row_cnt"}}{{)}}
>  {{private}} {{long}} {{rowCnt;}}|
>  
> Add new section in 'Advance Setting' tab when do cube design, user can set 
> table snapshot properties for each table, and by default, it is segment level 
> and store to metadata store
> h2. Build
> If user specify 'hbaseStore' storageType for any lookup table, will use 
> MapReduce job convert the hive source table to hfiles, and then bulk load 
> hfiles to HTable. So it will add two job steps to do the lookup table 
> materialization.
> h2. HBase Lookup Table Schema
> all data are stored in raw value
> suppose the lookup table has primary keys: key1,key2
> rowkey will be:
> ||2bytes||2 bytes||len1 bytes||2 bytes||len2 bytes||
> |shard|key1 value length(len1)|key1 value|key 2 value length(len2)|key2 value|
> the first 2 bytes is shard number, HBase table can be pre-split, the shard 
> size is configurable through Kylin's properties: 
> "kylin.snapshot.ext.shard-mb", default size is 500MB.
> 1 column family c, multiple columns which column name is the index of the 
> column in the table definition
> |c|
> |1|2|...|
>  
> h2. Query
> For key lookup query, directly call hbase get api to get entire row according 
> to key.
> For queries that need fetch keys according to the derived columns, iterate 
> all rows to get related keys.
> For queries that only hit the lookup table, iterate all rows and let calcite 
> to do aggregation and filter.
> h2. Management
> For each lookup table, admin can view how many snapshots it has in Kylin, and 
> can view each snapshot type/size information and which cube/segments

[jira] [Commented] (KYLIN-3321) Set MALLOC_ARENA_MAX in script

2018-04-02 Thread liyang (JIRA) 

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

liyang commented on KYLIN-3321:
---

Interesting information!! Thank you Ted!

> Set MALLOC_ARENA_MAX in script
> --
>
> Key: KYLIN-3321
> URL: https://issues.apache.org/jira/browse/KYLIN-3321
> Project: Kylin
>  Issue Type: Task
>Reporter: Ted Yu
>Priority: Major
>
> conf/setenv.sh would be good place to set MALLOC_ARENA_MAX which prevents 
> native memory OOM.
> See https://github.com/prestodb/presto/issues/8993



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

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

2018-04-02 Thread liyang (JIRA) 

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

liyang commented on KYLIN-3001:
---

Sorry I don't understand the patch. Replace "[ ]" with " ", replace a space 
with a space, what is the use?

> 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: Pan, Julian
>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-3290) Avoid calling Class#newInstance

2018-04-02 Thread Ted Yu (JIRA) 

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

Ted Yu updated KYLIN-3290:
--
Description: 
Class#newInstance is deprecated starting in Java 9 - 
https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw 
undeclared checked exceptions.


The suggested replacement is getDeclaredConstructor().newInstance(), which 
wraps the checked exceptions in InvocationException.

  was:
Class#newInstance is deprecated starting in Java 9 - 
https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw 
undeclared checked exceptions.

The suggested replacement is getDeclaredConstructor().newInstance(), which 
wraps the checked exceptions in InvocationException.


> Avoid calling Class#newInstance
> ---
>
> Key: KYLIN-3290
> URL: https://issues.apache.org/jira/browse/KYLIN-3290
> Project: Kylin
>  Issue Type: Task
>Reporter: Ted Yu
>Priority: Minor
>
> Class#newInstance is deprecated starting in Java 9 - 
> https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw 
> undeclared checked exceptions.
> The suggested replacement is getDeclaredConstructor().newInstance(), which 
> wraps the checked exceptions in InvocationException.



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

[jira] [Updated] (KYLIN-3295) Unused method SQLDigestUtil#appendTsFilterToExecute

2018-04-02 Thread Ted Yu (JIRA) 

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

Ted Yu updated KYLIN-3295:
--
Description: 
SQLDigestUtil#appendTsFilterToExecute is not called anywhere.

{code}
   T ret = action.apply(null);
{code}
Passing null to {{apply}} seems incorrect.

  was:
SQLDigestUtil#appendTsFilterToExecute is not called anywhere.

Also
{code}
   T ret = action.apply(null);
{code}
Passing null to {{apply}} seems incorrect.


> Unused method SQLDigestUtil#appendTsFilterToExecute
> ---
>
> Key: KYLIN-3295
> URL: https://issues.apache.org/jira/browse/KYLIN-3295
> Project: Kylin
>  Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> SQLDigestUtil#appendTsFilterToExecute is not called anywhere.
> {code}
>T ret = action.apply(null);
> {code}
> Passing null to {{apply}} seems incorrect.



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

[jira] [Closed] (KYLIN-3323) Allow debugTomcat add more arguments

2018-04-02 Thread yongjie zhao (JIRA) 

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

yongjie zhao closed KYLIN-3323.
---
Resolution: Fixed

> Allow debugTomcat add more arguments
> 
>
> Key: KYLIN-3323
> URL: https://issues.apache.org/jira/browse/KYLIN-3323
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yongjie zhao
>Assignee: yongjie zhao
>Priority: Minor
> Attachments: Screen Shot 2018-03-28 at 3.05.00 PM.png
>
>
> On current, debugTomcat only accepts port argument. I must edit 
> kylin.property for execute remote command, such as 
> kylin.job.use-remote-cli=true.  This issue can be passed arguments for 
> debugTomcat



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

[jira] [Comment Edited] (KYLIN-3323) Allow debugTomcat add more arguments

2018-04-02 Thread yongjie zhao (JIRA) 

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

yongjie zhao edited comment on KYLIN-3323 at 4/2/18 9:06 AM:
-

thank you for remind. I will close this issue.


was (Author: zog):
thank you for remind.

> Allow debugTomcat add more arguments
> 
>
> Key: KYLIN-3323
> URL: https://issues.apache.org/jira/browse/KYLIN-3323
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yongjie zhao
>Assignee: yongjie zhao
>Priority: Minor
> Attachments: Screen Shot 2018-03-28 at 3.05.00 PM.png
>
>
> On current, debugTomcat only accepts port argument. I must edit 
> kylin.property for execute remote command, such as 
> kylin.job.use-remote-cli=true.  This issue can be passed arguments for 
> debugTomcat



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

[jira] [Commented] (KYLIN-3323) Allow debugTomcat add more arguments

2018-04-02 Thread yongjie zhao (JIRA) 

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

yongjie zhao commented on KYLIN-3323:
-

thank you for remind.

> Allow debugTomcat add more arguments
> 
>
> Key: KYLIN-3323
> URL: https://issues.apache.org/jira/browse/KYLIN-3323
> Project: Kylin
>  Issue Type: Improvement
>Reporter: yongjie zhao
>Assignee: yongjie zhao
>Priority: Minor
> Attachments: Screen Shot 2018-03-28 at 3.05.00 PM.png
>
>
> On current, debugTomcat only accepts port argument. I must edit 
> kylin.property for execute remote command, such as 
> kylin.job.use-remote-cli=true.  This issue can be passed arguments for 
> debugTomcat



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

[jira] [Assigned] (KYLIN-3294) Remove HBaseMROutput.java, RangeKeyDistributionJob.java and other sunset classes

2018-04-02 Thread Wenzheng Liu (JIRA) 

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

Wenzheng Liu reassigned KYLIN-3294:
---

Assignee: Wenzheng Liu

> Remove HBaseMROutput.java, RangeKeyDistributionJob.java and other sunset 
> classes
> 
>
> Key: KYLIN-3294
> URL: https://issues.apache.org/jira/browse/KYLIN-3294
> Project: Kylin
>  Issue Type: Improvement
>  Components: Job Engine
>Reporter: Shaofeng SHI
>Assignee: Wenzheng Liu
>Priority: Major
>
> They were legacy classes, keeping them will add maintainence effort 
> especially when upgrade HBase version. Should delete them.



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