[jira] [Commented] (KYLIN-5278) Support Pivot feature of SQL
[ https://issues.apache.org/jira/browse/KYLIN-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17620784#comment-17620784 ] yoonsung.lee commented on KYLIN-5278: - OK. I see, thanks to response :) > Support Pivot feature of SQL > > > Key: KYLIN-5278 > URL: https://issues.apache.org/jira/browse/KYLIN-5278 > Project: Kylin > Issue Type: Wish > Components: Query Engine >Reporter: yoonsung.lee >Priority: Major > > HI. I'm using Kylin 3.1.3 for OLAP. > It seems that there is no feature of Pivot. (e.g. > https://docs.data.world/documentation/sql/concepts/advanced/PIVOT.html , > https://calcite.apache.org/javadocAggregate/org/apache/calcite/sql/SqlPivot.html > ) > I also tried to find source code related to Pivot, but there isn't. > Is there no feature for Pivot in Kylin(3 or 4)? > If not, is there a plan? > If not, is there a way to write a query like Pivot? > Best regards :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5278) Support Pivot feature of SQL
yoonsung.lee created KYLIN-5278: --- Summary: Support Pivot feature of SQL Key: KYLIN-5278 URL: https://issues.apache.org/jira/browse/KYLIN-5278 Project: Kylin Issue Type: Wish Components: Query Engine Reporter: yoonsung.lee HI. I'm using Kylin 3.1.3 for OLAP. It seems that there is no feature of Pivot. (e.g. https://docs.data.world/documentation/sql/concepts/advanced/PIVOT.html , https://calcite.apache.org/javadocAggregate/org/apache/calcite/sql/SqlPivot.html ) I also tried to find source code related to Pivot, but there isn't. Is there no feature for Pivot in Kylin(3 or 4)? If not, is there a plan? If not, is there a way to write a query like Pivot? Best regards :) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
[ https://issues.apache.org/jira/browse/KYLIN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-5259: Component/s: Documentation > Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL > -- > > Key: KYLIN-5259 > URL: https://issues.apache.org/jira/browse/KYLIN-5259 > Project: Kylin > Issue Type: Wish > Components: Documentation >Affects Versions: v3.1.3 >Reporter: yoonsung.lee >Priority: Major > > Hi. I have been using Kylin 3.1.3. > Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * > means series of functions such as day, day_of_week, day_of_month, > day_of_year. > Are there existing features to support these? > If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
[ https://issues.apache.org/jira/browse/KYLIN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1760#comment-1760 ] yoonsung.lee commented on KYLIN-5259: - I tried them and they work fine. Thanks to respond :) > Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL > -- > > Key: KYLIN-5259 > URL: https://issues.apache.org/jira/browse/KYLIN-5259 > Project: Kylin > Issue Type: Wish >Affects Versions: v3.1.3 >Reporter: yoonsung.lee >Priority: Major > > Hi. I have been using Kylin 3.1.3. > Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * > means series of functions such as day, day_of_week, day_of_month, > day_of_year. > Are there existing features to support these? > If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
[ https://issues.apache.org/jira/browse/KYLIN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-5259: Description: Hi. I have been using Kylin 3.1.3. Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * means series of functions such as day, day_of_week, day_of_month, day_of_year. Are there existing features to support these? If not, is there any plan to support these? was: Hi. Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * means series of functions such as day, day_of_week, day_of_month, day_of_year. Are there existing features to support these? If not, is there any plan to support these? > Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL > -- > > Key: KYLIN-5259 > URL: https://issues.apache.org/jira/browse/KYLIN-5259 > Project: Kylin > Issue Type: Wish >Affects Versions: v3.1.3 >Reporter: yoonsung.lee >Priority: Major > > Hi. I have been using Kylin 3.1.3. > Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * > means series of functions such as day, day_of_week, day_of_month, > day_of_year. > Are there existing features to support these? > If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
yoonsung.lee created KYLIN-5259: --- Summary: Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL Key: KYLIN-5259 URL: https://issues.apache.org/jira/browse/KYLIN-5259 Project: Kylin Issue Type: Wish Reporter: yoonsung.lee Hi. Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * means series of functions such as day, day_of_week, day_of_month, day_of_year. Are there existing features to support these? If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5259) Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL
[ https://issues.apache.org/jira/browse/KYLIN-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-5259: Affects Version/s: v3.1.3 > Support DAY*, WEEK*, MONTH*, YEAR* functions from SQL > -- > > Key: KYLIN-5259 > URL: https://issues.apache.org/jira/browse/KYLIN-5259 > Project: Kylin > Issue Type: Wish >Affects Versions: v3.1.3 >Reporter: yoonsung.lee >Priority: Major > > Hi. > Kylin's SQL seems to do not support DAY*, WEEK*, MONTH*, YEAR* functions. * > means series of functions such as day, day_of_week, day_of_month, > day_of_year. > Are there existing features to support these? > If not, is there any plan to support these? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KYLIN-4544) Kylin on Parquet LEFT JOIN Query failed
[ https://issues.apache.org/jira/browse/KYLIN-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317800#comment-17317800 ] yoonsung.lee commented on KYLIN-4544: - [~wangrupeng] Let me know which version you failed. > Kylin on Parquet LEFT JOIN Query failed > --- > > Key: KYLIN-4544 > URL: https://issues.apache.org/jira/browse/KYLIN-4544 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Reporter: bright liao >Assignee: Wang Rupeng >Priority: Major > Fix For: v4.0.0-GA > > > select t.n,t1.n from ( > select count(*) as n from dm.dm_bi_device_info_day where > deal_date='20200527') as t > LEFT JOIN ( > select count(*) as n from dm.dm_bi_device_info_day where > deal_date='20200526') as t1 > on 1=1 > This sql execute failed while kylin-3.0 runs with no problem. > Error message： > Error while applying rule OLAPJoinRule, args > [rel#234029:LogicalJoin.NONE.[](left=rel#234022:Subset#3.NONE.[],right=rel#234028:Subset#6.NONE.[],condition==(1, > 1),joinType=left)] while executing SQL: "select * from (select t.n,t1.n from > ( select count(*) as n from dm.dm_bi_device_info_day where > deal_date='20200527') as t LEFT JOIN ( select count(*) as n from > dm.dm_bi_device_info_day where deal_date='20200526') as t1 on 1=1) limit > 5" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (KYLIN-4847) Cuboid to HFile step failed on multiple job server env because of trying to read the metric jar file from the inactive job server's location.
[
https://issues.apache.org/jira/browse/KYLIN-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yoonsung.lee resolved KYLIN-4847.
-
Fix Version/s: v3.1.2
Resolution: Fixed
> Cuboid to HFile step failed on multiple job server env because of trying to
> read the metric jar file from the inactive job server's location.
> -
>
> Key: KYLIN-4847
> URL: https://issues.apache.org/jira/browse/KYLIN-4847
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v3.1.0
>Reporter: yoonsung.lee
>Assignee: yoonsung.lee
>Priority: Major
> Fix For: v3.1.2
>
>
> h1. My Cluster Setting
> 1. versIon: 3.1.0
> 2. 2 job servers(job & query mode), 2 query only servers. Each of them runs
> on each different host machine.
> 3. Use spark engine to build job.
> h1. Problem Circumstance
> h2. Root cause
> The active job server submits spark job to execute `Convert Cuboid Data to
> HFile`. But the active job server get an error because a resource for
> submitting spark job has the wrong path which the active job server cannot
> read.
> * wrong resource:
> ${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
> * The ${KYLIN_HOME} is the inactive job server's location for only the above
> jar file.
> This situation occurs in the following two circumstances.
> h2. On build cube
> 1. Request the build API to the inactive job server. (exactly:
> /kylin/api/cubes/${cube_name}/rebuild )
> 2. Inactive job server stores the build task in meta store.
> 3. Active job server takes the build task and proceeds it.
> 4. Active job server failed on the `Convert Cuboid Data to HFile` step.
> **This doesn't occur when I request build API to the active job server.**
> h2. On merge
> 1. Trigger merge cube job periodically
> 2. Active job server takes the merge task and proceeds it.
> 3. Active job server failed on the `Convert Cuboid Data to HFile` step.
> **This doesn't occur when there is only one job server in the cluster.**
> h1. Progress to solve this.
> I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
> Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
> the `Cuboid to HFile` spark job.
> *
> [https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69]
> h1. Questions
> 1. I'm trying to remote debug with IDE to make sure my guess is right. But
> the breakpoint on that line is not captured on Runtime. It seems to be called
> on the booting phase. Is it right?
> 2. Is there any hint or guessing to solve this issue regardless of the above
> my progress?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KYLIN-4856) Website guide is not matched with ciwki about Job Scheduler
[
https://issues.apache.org/jira/browse/KYLIN-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258033#comment-17258033
]
yoonsung.lee edited comment on KYLIN-4856 at 1/4/21, 7:53 AM:
--
[~zhangyaqian]Thanks for your reply.
Resolve this issue after fix the cwiki.
was (Author: yoonsung.lee):
[~zhangyaqian]Thanks for your reply.
Close this issue after fix the cwiki.
> Website guide is not matched with ciwki about Job Scheduler
> ---
>
> Key: KYLIN-4856
> URL: https://issues.apache.org/jira/browse/KYLIN-4856
> Project: Kylin
> Issue Type: Bug
> Components: Website
>Affects Versions: v3.1.1
>Reporter: yoonsung.lee
>Assignee: yoonsung.lee
>Priority: Major
>
> Hi. I'm yoonsung.lee
> I'm trying to apply distributed multiple job schedulers to my cluster.
> But the explanations of distributed multiple job schedulers are different
> between the website and cwiki.
> h3. Website
> The website ({color:red}Enable multiple job engines (HA){color} section in
> {color:#0747A6}http://kylin.apache.org/docs/install/advance_settings.html{color})
> guide to configure
> {code}
> kylin.job.scheduler.default=2
> kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock
> {code}
> for multiple job engines.
> h3. Cwiki
> The cwiki
> ({color:#0747A6}https://cwiki.apache.org/confluence/display/KYLIN/Comparison+of+Kylin+Job+scheduler{color})
> says the *DistributedScheduler* (which is set as
> *kylin.job.scheduler.default=2*) uses ZookeeperDistributedLock as
> implementation class.
> But the website guides to set
> *kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock* which
> is described as DefaultScheduler in cwiki.
> h1. Solution
> If the cwiki is right, the description on the website should be changed.
> If the website is right, the description on the cwiki should be changed.
> Please let me know if I misunderstand for setting distributed multiple job
> schedulers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KYLIN-4856) Website guide is not matched with ciwki about Job Scheduler
[
https://issues.apache.org/jira/browse/KYLIN-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258033#comment-17258033
]
yoonsung.lee commented on KYLIN-4856:
-
[~zhangyaqian]Thanks for your reply.
Close this issue after fix the cwiki.
> Website guide is not matched with ciwki about Job Scheduler
> ---
>
> Key: KYLIN-4856
> URL: https://issues.apache.org/jira/browse/KYLIN-4856
> Project: Kylin
> Issue Type: Bug
> Components: Website
>Affects Versions: v3.1.1
>Reporter: yoonsung.lee
>Priority: Major
>
> Hi. I'm yoonsung.lee
> I'm trying to apply distributed multiple job schedulers to my cluster.
> But the explanations of distributed multiple job schedulers are different
> between the website and cwiki.
> h3. Website
> The website ({color:red}Enable multiple job engines (HA){color} section in
> {color:#0747A6}http://kylin.apache.org/docs/install/advance_settings.html{color})
> guide to configure
> {code}
> kylin.job.scheduler.default=2
> kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock
> {code}
> for multiple job engines.
> h3. Cwiki
> The cwiki
> ({color:#0747A6}https://cwiki.apache.org/confluence/display/KYLIN/Comparison+of+Kylin+Job+scheduler{color})
> says the *DistributedScheduler* (which is set as
> *kylin.job.scheduler.default=2*) uses ZookeeperDistributedLock as
> implementation class.
> But the website guides to set
> *kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock* which
> is described as DefaultScheduler in cwiki.
> h1. Solution
> If the cwiki is right, the description on the website should be changed.
> If the website is right, the description on the cwiki should be changed.
> Please let me know if I misunderstand for setting distributed multiple job
> schedulers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KYLIN-4856) Website guide is not matched with ciwki about Job Scheduler
[
https://issues.apache.org/jira/browse/KYLIN-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yoonsung.lee reassigned KYLIN-4856:
---
Assignee: yoonsung.lee
> Website guide is not matched with ciwki about Job Scheduler
> ---
>
> Key: KYLIN-4856
> URL: https://issues.apache.org/jira/browse/KYLIN-4856
> Project: Kylin
> Issue Type: Bug
> Components: Website
>Affects Versions: v3.1.1
>Reporter: yoonsung.lee
>Assignee: yoonsung.lee
>Priority: Major
>
> Hi. I'm yoonsung.lee
> I'm trying to apply distributed multiple job schedulers to my cluster.
> But the explanations of distributed multiple job schedulers are different
> between the website and cwiki.
> h3. Website
> The website ({color:red}Enable multiple job engines (HA){color} section in
> {color:#0747A6}http://kylin.apache.org/docs/install/advance_settings.html{color})
> guide to configure
> {code}
> kylin.job.scheduler.default=2
> kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock
> {code}
> for multiple job engines.
> h3. Cwiki
> The cwiki
> ({color:#0747A6}https://cwiki.apache.org/confluence/display/KYLIN/Comparison+of+Kylin+Job+scheduler{color})
> says the *DistributedScheduler* (which is set as
> *kylin.job.scheduler.default=2*) uses ZookeeperDistributedLock as
> implementation class.
> But the website guides to set
> *kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock* which
> is described as DefaultScheduler in cwiki.
> h1. Solution
> If the cwiki is right, the description on the website should be changed.
> If the website is right, the description on the cwiki should be changed.
> Please let me know if I misunderstand for setting distributed multiple job
> schedulers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KYLIN-4856) Website guide is not matched with ciwki about Job Scheduler
[
https://issues.apache.org/jira/browse/KYLIN-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yoonsung.lee updated KYLIN-4856:
Issue Type: Bug (was: Task)
> Website guide is not matched with ciwki about Job Scheduler
> ---
>
> Key: KYLIN-4856
> URL: https://issues.apache.org/jira/browse/KYLIN-4856
> Project: Kylin
> Issue Type: Bug
> Components: Website
>Affects Versions: v3.1.1
>Reporter: yoonsung.lee
>Priority: Major
>
> Hi. I'm yoonsung.lee
> I'm trying to apply distributed multiple job schedulers to my cluster.
> But the explanations of distributed multiple job schedulers are different
> between the website and cwiki.
> h3. Website
> The website ({color:red}Enable multiple job engines (HA){color} section in
> {color:#0747A6}http://kylin.apache.org/docs/install/advance_settings.html{color})
> guide to configure
> {code}
> kylin.job.scheduler.default=2
> kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock
> {code}
> for multiple job engines.
> h3. Cwiki
> The cwiki
> ({color:#0747A6}https://cwiki.apache.org/confluence/display/KYLIN/Comparison+of+Kylin+Job+scheduler{color})
> says the *DistributedScheduler* (which is set as
> *kylin.job.scheduler.default=2*) uses ZookeeperDistributedLock as
> implementation class.
> But the website guides to set
> *kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock* which
> is described as DefaultScheduler in cwiki.
> h1. Solution
> If the cwiki is right, the description on the website should be changed.
> If the website is right, the description on the cwiki should be changed.
> Please let me know if I misunderstand for setting distributed multiple job
> schedulers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KYLIN-4856) Website guide is not matched with ciwki about Job Scheduler
yoonsung.lee created KYLIN-4856:
---
Summary: Website guide is not matched with ciwki about Job
Scheduler
Key: KYLIN-4856
URL: https://issues.apache.org/jira/browse/KYLIN-4856
Project: Kylin
Issue Type: Task
Components: Website
Affects Versions: v3.1.1
Reporter: yoonsung.lee
Hi. I'm yoonsung.lee
I'm trying to apply distributed multiple job schedulers to my cluster.
But the explanations of distributed multiple job schedulers are different
between the website and cwiki.
h3. Website
The website ({color:red}Enable multiple job engines (HA){color} section in
{color:#0747A6}http://kylin.apache.org/docs/install/advance_settings.html{color})
guide to configure
{code}
kylin.job.scheduler.default=2
kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock
{code}
for multiple job engines.
h3. Cwiki
The cwiki
({color:#0747A6}https://cwiki.apache.org/confluence/display/KYLIN/Comparison+of+Kylin+Job+scheduler{color})
says the *DistributedScheduler* (which is set as
*kylin.job.scheduler.default=2*) uses ZookeeperDistributedLock as
implementation class.
But the website guides to set
*kylin.job.lock=org.apache.kylin.storage.hbase.util.ZookeeperJobLock* which is
described as DefaultScheduler in cwiki.
h1. Solution
If the cwiki is right, the description on the website should be changed.
If the website is right, the description on the cwiki should be changed.
Please let me know if I misunderstand for setting distributed multiple job
schedulers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KYLIN-4847) Cuboid to HFile step failed on multiple job server env because of trying to read the metric jar file from the inactive job server's location.
[
https://issues.apache.org/jira/browse/KYLIN-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yoonsung.lee reassigned KYLIN-4847:
---
Assignee: yoonsung.lee
> Cuboid to HFile step failed on multiple job server env because of trying to
> read the metric jar file from the inactive job server's location.
> -
>
> Key: KYLIN-4847
> URL: https://issues.apache.org/jira/browse/KYLIN-4847
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v3.1.0
>Reporter: yoonsung.lee
>Assignee: yoonsung.lee
>Priority: Major
>
> h1. My Cluster Setting
> 1. versIon: 3.1.0
> 2. 2 job servers(job & query mode), 2 query only servers. Each of them runs
> on each different host machine.
> 3. Use spark engine to build job.
> h1. Problem Circumstance
> h2. Root cause
> The active job server submits spark job to execute `Convert Cuboid Data to
> HFile`. But the active job server get an error because a resource for
> submitting spark job has the wrong path which the active job server cannot
> read.
> * wrong resource:
> ${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
> * The ${KYLIN_HOME} is the inactive job server's location for only the above
> jar file.
> This situation occurs in the following two circumstances.
> h2. On build cube
> 1. Request the build API to the inactive job server. (exactly:
> /kylin/api/cubes/${cube_name}/rebuild )
> 2. Inactive job server stores the build task in meta store.
> 3. Active job server takes the build task and proceeds it.
> 4. Active job server failed on the `Convert Cuboid Data to HFile` step.
> **This doesn't occur when I request build API to the active job server.**
> h2. On merge
> 1. Trigger merge cube job periodically
> 2. Active job server takes the merge task and proceeds it.
> 3. Active job server failed on the `Convert Cuboid Data to HFile` step.
> **This doesn't occur when there is only one job server in the cluster.**
> h1. Progress to solve this.
> I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
> Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
> the `Cuboid to HFile` spark job.
> *
> [https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69]
> h1. Questions
> 1. I'm trying to remote debug with IDE to make sure my guess is right. But
> the breakpoint on that line is not captured on Runtime. It seems to be called
> on the booting phase. Is it right?
> 2. Is there any hint or guessing to solve this issue regardless of the above
> my progress?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (KYLIN-4834) Auto forward the job API request to the available leader job server
[ https://issues.apache.org/jira/browse/KYLIN-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee closed KYLIN-4834. --- It is not a issue > Auto forward the job API request to the available leader job server > --- > > Key: KYLIN-4834 > URL: https://issues.apache.org/jira/browse/KYLIN-4834 > Project: Kylin > Issue Type: Wish > Components: Others >Reporter: yoonsung.lee >Priority: Minor > Fix For: all > > > Hi. I'm yoonsung.lee developing & operating the statistical storage using > Kylin in LINE Advertising dept. > h1. Current Situation > I understand there is only one active leader job server instance in a Kylin > cluster. > The leader job server is selected by Zookeeper if there are multiple active > job servers in a Kylin cluster. > This is my pain point. > When my leader job server has a fault or shutdown, I want to change the > leader job server automatically and the DNS server route the traffic to the > changed one. > In this case, I should know which one is the leader job server as soon as > possible the leader(active) has changed. > For this one, I try to watch the path of Zookeeper in which the Kylin server > maintains the server list in a cluster. > But, this approach has a fault in essence. It's not an implementation > controlled by Kylin. > h1. Question > Is my approach appropriate for the Kylin cluster? > If not, is there any better idea for fault tolerance of job servers with auto > DNS or LoadBalancer mapping? > h1. Suggestion > So, I suggest this idea. > Any server in a Kylin cluster forwards the API request to the leader job > server in the case that the request should be done by the job server and pass > valid authentication. If then, I just attach all of the servers to my > LoadBalancer without caring about which one is the leader job server. > * Could this feature be harmful or have side-effects? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4834) Auto forward the job API request to the available leader job server
[ https://issues.apache.org/jira/browse/KYLIN-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253945#comment-17253945 ] yoonsung.lee commented on KYLIN-4834: - [~zhangyaqian][~xxyu][~shaofengshi] Thanks all of you. I re-try to run multiple job servers on a cluster. I checked the job which was provided from the inactive job server is stored in the meta-store and the active job server takes and proceeds it. But there was a problem in the multiple job servers environment. I write it on another issue. I will be glad that you help to solve this issue. https://issues.apache.org/jira/browse/KYLIN-4847 > Auto forward the job API request to the available leader job server > --- > > Key: KYLIN-4834 > URL: https://issues.apache.org/jira/browse/KYLIN-4834 > Project: Kylin > Issue Type: Wish > Components: Others >Reporter: yoonsung.lee >Priority: Minor > Fix For: all > > > Hi. I'm yoonsung.lee developing & operating the statistical storage using > Kylin in LINE Advertising dept. > h1. Current Situation > I understand there is only one active leader job server instance in a Kylin > cluster. > The leader job server is selected by Zookeeper if there are multiple active > job servers in a Kylin cluster. > This is my pain point. > When my leader job server has a fault or shutdown, I want to change the > leader job server automatically and the DNS server route the traffic to the > changed one. > In this case, I should know which one is the leader job server as soon as > possible the leader(active) has changed. > For this one, I try to watch the path of Zookeeper in which the Kylin server > maintains the server list in a cluster. > But, this approach has a fault in essence. It's not an implementation > controlled by Kylin. > h1. Question > Is my approach appropriate for the Kylin cluster? > If not, is there any better idea for fault tolerance of job servers with auto > DNS or LoadBalancer mapping? > h1. Suggestion > So, I suggest this idea. > Any server in a Kylin cluster forwards the API request to the leader job > server in the case that the request should be done by the job server and pass > valid authentication. If then, I just attach all of the servers to my > LoadBalancer without caring about which one is the leader job server. > * Could this feature be harmful or have side-effects? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4847) Cuboid to HFile step failed on multiple job server env because of trying to read the metric jar file from the inactive job server's location.
[
https://issues.apache.org/jira/browse/KYLIN-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yoonsung.lee updated KYLIN-4847:
Description:
h1. My Cluster Setting
1. versIon: 3.1.0
2. 2 job servers(job & query mode), 2 query only servers. Each of them runs on
each different host machine.
3. Use spark engine to build job.
h1. Problem Circumstance
h2. Root cause
The active job server submits spark job to execute `Convert Cuboid Data to
HFile`. But the active job server get an error because a resource for
submitting spark job has the wrong path which the active job server cannot read.
* wrong resource:
${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
* The ${KYLIN_HOME} is the inactive job server's location for only the above
jar file.
This situation occurs in the following two circumstances.
h2. On build cube
1. Request the build API to the inactive job server. (exactly:
/kylin/api/cubes/${cube_name}/rebuild )
2. Inactive job server stores the build task in meta store.
3. Active job server takes the build task and proceeds it.
4. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when I request build API to the active job server.**
h2. On merge
1. Trigger merge cube job periodically
2. Active job server takes the merge task and proceeds it.
3. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when there is only one job server in the cluster.**
h1. Progress to solve this.
I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
the `Cuboid to HFile` spark job.
*
[https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69]
h1. Questions
1. I'm trying to remote debug with IDE to make sure my guess is right. But the
breakpoint on that line is not captured on Runtime. It seems to be called on
the booting phase. Is it right?
2. Is there any hint or guessing to solve this issue regardless of the above my
progress?
was:
h1. My Cluster Setting
1. versIon: 3.1.0
2. 2 job servers(job & query mode), 2 query only servers. Each of them runs on
each different host machine.
3. Use spark engine to build job.
h1. Problem Circumstance
h2. Root cause
The active job server submits spark job to execute `Convert Cuboid Data to
HFile`. But the active job server get an error because a resource for
submitting spark job has the wrong path which the active job server cannot read.
* wrong resource:
${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
* The ${KYLIN_HOME} is the inactive job server's location for only the above
jar file.
This situation occurs in the following two circumstances.
h2. On build cube
1. Request the build API to the inactive job server. (exactly:
/kylin/api/cubes/{cube_name}/rebuild )
2. Inactive job server stores the build task in meta store.
3. Active job server takes the build task and proceeds it.
4. Active job server failed on the `Convert Cuboid Data to HFile` step.
** This doesn't occur when I request build API to the active job server. **
h2. On merge
1. Trigger merge cube job periodically
2. Active job server takes the merge task and proceeds it.
3. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when there is only one job server in the cluster.**
h1. Progress to solve this.
I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
the `Cuboid to HFile` spark job.
*
https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69
h1. Questions
1. I'm trying to remote debug with IDE to make sure my guess is right. But the
breakpoint on that line is not captured on Runtime. It seems to be called on
the booting phase. Is it right?
2. Is there any hint or guessing to solve this issue regardless of the above my
progress?
> Cuboid to HFile step failed on multiple job server env because of trying to
> read the metric jar file from the inactive job server's location.
> -
>
> Key: KYLIN-4847
> URL: https://issues.apache.org/jira/browse/KYLIN-4847
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v3.1.0
>Reporter: yoonsung.lee
>Priority: Major
>
> h1. My Cluster Setting
> 1. versIon: 3.1.0
> 2. 2 job servers(job & query mode), 2 query only servers. Each of them runs
> on each different host machine.
> 3. Use spark engine to
[jira] [Updated] (KYLIN-4847) Cuboid to HFile step failed on multiple job server env because of trying to read the metric jar file from the inactive job server's location.
[
https://issues.apache.org/jira/browse/KYLIN-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yoonsung.lee updated KYLIN-4847:
Description:
h1. My Cluster Setting
1. versIon: 3.1.0
2. 2 job servers(job & query mode), 2 query only servers. Each of them runs on
each different host machine.
3. Use spark engine to build job.
h1. Problem Circumstance
h2. Root cause
The active job server submits spark job to execute `Convert Cuboid Data to
HFile`. But the active job server get an error because a resource for
submitting spark job has the wrong path which the active job server cannot read.
* wrong resource:
${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
* The ${KYLIN_HOME} is the inactive job server's location for only the above
jar file.
This situation occurs in the following two circumstances.
h2. On build cube
1. Request the build API to the inactive job server. (exactly:
/kylin/api/cubes/{cube_name}/rebuild )
2. Inactive job server stores the build task in meta store.
3. Active job server takes the build task and proceeds it.
4. Active job server failed on the `Convert Cuboid Data to HFile` step.
** This doesn't occur when I request build API to the active job server. **
h2. On merge
1. Trigger merge cube job periodically
2. Active job server takes the merge task and proceeds it.
3. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when there is only one job server in the cluster.**
h1. Progress to solve this.
I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
the `Cuboid to HFile` spark job.
*
https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69
h1. Questions
1. I'm trying to remote debug with IDE to make sure my guess is right. But the
breakpoint on that line is not captured on Runtime. It seems to be called on
the booting phase. Is it right?
2. Is there any hint or guessing to solve this issue regardless of the above my
progress?
was:
h1. My Cluster Setting
1. versIon: 3.1.0
2. 2 job servers(job & query mode), 2 query only servers. Each of them runs on
each different host machine.
3. Use spark engine to build job.
h1. Problem Circumstance
h2. Root cause
The active job server submits spark job to execute `Convert Cuboid Data to
HFile`. But the active job server get an error because a resource for
submitting spark job has the wrong path which the active job server cannot read.
* wrong resource:
${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
* The ${KYLIN_HOME} is the inactive job server's location for only the above
jar file.
This situation occurs in the following two circumstances.
h2. On build cube
1. Request the build API to the inactive job server.
* exactly: /kylin/api/cubes/{cube_name}/rebuild
2. Inactive job server stores the build task in meta store.
3. Active job server takes the build task and proceeds it.
4. Active job server failed on the `Convert Cuboid Data to HFile` step.
** This doesn't occur when I request build API to the active job server. **
h2. On merge
1. Trigger merge cube job periodically
2. Active job server takes the merge task and proceeds it.
3. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when there is only one job server in the cluster.**
h1. Progress to solve this.
I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
the `Cuboid to HFile` spark job.
*
https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69
h1. Questions
1. I'm trying to remote debug with IDE to make sure my guess is right. But the
breakpoint on that line is not captured on Runtime. It seems to be called on
the booting phase. Is it right?
2. Is there any hint or guessing to solve this issue regardless of the above my
progress?
> Cuboid to HFile step failed on multiple job server env because of trying to
> read the metric jar file from the inactive job server's location.
> -
>
> Key: KYLIN-4847
> URL: https://issues.apache.org/jira/browse/KYLIN-4847
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v3.1.0
>Reporter: yoonsung.lee
>Priority: Major
>
> h1. My Cluster Setting
> 1. versIon: 3.1.0
> 2. 2 job servers(job & query mode), 2 query only servers. Each of them runs
> on each different host machine.
> 3. Use spark engine to build job.
[jira] [Updated] (KYLIN-4847) Cuboid to HFile step failed on multiple job server env because of trying to read the metric jar file from the inactive job server's location.
[
https://issues.apache.org/jira/browse/KYLIN-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yoonsung.lee updated KYLIN-4847:
Description:
h1. My Cluster Setting
1. versIon: 3.1.0
2. 2 job servers(job & query mode), 2 query only servers. Each of them runs on
each different host machine.
3. Use spark engine to build job.
h1. Problem Circumstance
h2. Root cause
The active job server submits spark job to execute `Convert Cuboid Data to
HFile`. But the active job server get an error because a resource for
submitting spark job has the wrong path which the active job server cannot read.
* wrong resource:
${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
* The ${KYLIN_HOME} is the inactive job server's location for only the above
jar file.
This situation occurs in the following two circumstances.
h2. On build cube
1. Request the build API to the inactive job server.
* exactly: /kylin/api/cubes/{cube_name}/rebuild
2. Inactive job server stores the build task in meta store.
3. Active job server takes the build task and proceeds it.
4. Active job server failed on the `Convert Cuboid Data to HFile` step.
** This doesn't occur when I request build API to the active job server. **
h2. On merge
1. Trigger merge cube job periodically
2. Active job server takes the merge task and proceeds it.
3. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when there is only one job server in the cluster.**
h1. Progress to solve this.
I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
the `Cuboid to HFile` spark job.
*
https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69
h1. Questions
1. I'm trying to remote debug with IDE to make sure my guess is right. But the
breakpoint on that line is not captured on Runtime. It seems to be called on
the booting phase. Is it right?
2. Is there any hint or guessing to solve this issue regardless of the above my
progress?
was:
h1. My Cluster Setting
1. versIon: 3.1.0
2. 2 job servers(job & query mode), 2 query only servers. Each of them runs on
each different host machine.
3. Use spark engine to build job.
h1. Problem Circumstance
h2. Root cause
The active job server submits spark job to execute `Convert Cuboid Data to
HFile`. But the active job server get an error because a resource for
submitting spark job has the wrong path which the active job server cannot read.
* wrong resource:
${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
* The ${KYLIN_HOME} is the inactive job server's location for only the above
jar file.
This situation occurs in the following two circumstances.
h2. On build cube
1. Request the build API to the inactive job server.
* exactly: /kylin/api/cubes/{cube_name}/rebuild
2. Inactive job server stores the build task in meta store.
3. Active job server takes the build task and proceeds it.
4. Active job server failed on the `Convert Cuboid Data to HFile` step.
** This doesn't occur when I request build API to the active job server. **
h2. On merge
1. Trigger merge cube job periodically
2. Active job server takes the merge task and proceeds it.
3. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when there is only one job server in the cluster.**
h1. Progress to solve this.
I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
the `Cuboid to HFile` spark job.
*
https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69
h1. Questions
1. I'm trying to remote debug with IDE to make sure my guess is right. But the
breakpoint on that line is not captured on Runtime. It seems to be called on
the booting phase. Is it right?
2. Is there any hint or guessing to solve this issue regardless of the above my
progress?
> Cuboid to HFile step failed on multiple job server env because of trying to
> read the metric jar file from the inactive job server's location.
> -
>
> Key: KYLIN-4847
> URL: https://issues.apache.org/jira/browse/KYLIN-4847
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v3.1.0
>Reporter: yoonsung.lee
>Priority: Major
>
> h1. My Cluster Setting
> 1. versIon: 3.1.0
> 2. 2 job servers(job & query mode), 2 query only servers. Each of them runs
> on each different host machine.
> 3. Use spark engine to build job.
[jira] [Created] (KYLIN-4847) Cuboid to HFile step failed on multiple job server env because of trying to read the metric jar file from the inactive job server's location.
yoonsung.lee created KYLIN-4847:
---
Summary: Cuboid to HFile step failed on multiple job server env
because of trying to read the metric jar file from the inactive job server's
location.
Key: KYLIN-4847
URL: https://issues.apache.org/jira/browse/KYLIN-4847
Project: Kylin
Issue Type: Bug
Components: Job Engine
Affects Versions: v3.1.0
Reporter: yoonsung.lee
h1. My Cluster Setting
1. versIon: 3.1.0
2. 2 job servers(job & query mode), 2 query only servers. Each of them runs on
each different host machine.
3. Use spark engine to build job.
h1. Problem Circumstance
h2. Root cause
The active job server submits spark job to execute `Convert Cuboid Data to
HFile`. But the active job server get an error because a resource for
submitting spark job has the wrong path which the active job server cannot read.
* wrong resource:
${KYLIN_HOME}/tomcat/webapps/kylin/WEB-INF/lib/metrics-core-2.2.0.jar
* The ${KYLIN_HOME} is the inactive job server's location for only the above
jar file.
This situation occurs in the following two circumstances.
h2. On build cube
1. Request the build API to the inactive job server.
* exactly: /kylin/api/cubes/{cube_name}/rebuild
2. Inactive job server stores the build task in meta store.
3. Active job server takes the build task and proceeds it.
4. Active job server failed on the `Convert Cuboid Data to HFile` step.
** This doesn't occur when I request build API to the active job server. **
h2. On merge
1. Trigger merge cube job periodically
2. Active job server takes the merge task and proceeds it.
3. Active job server failed on the `Convert Cuboid Data to HFile` step.
**This doesn't occur when there is only one job server in the cluster.**
h1. Progress to solve this.
I'm trying to find which code set the metrics-core-2.2.0.jar path wrong.
Until now, I guess this code would be the set the metrics-core-2.2.0.jar for
the `Cuboid to HFile` spark job.
*
https://github.com/apache/kylin/blob/kylin-3.1.0/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/HBaseSparkSteps.java#L69
h1. Questions
1. I'm trying to remote debug with IDE to make sure my guess is right. But the
breakpoint on that line is not captured on Runtime. It seems to be called on
the booting phase. Is it right?
2. Is there any hint or guessing to solve this issue regardless of the above my
progress?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KYLIN-4834) Auto forward the job API request to the available leader job server
[ https://issues.apache.org/jira/browse/KYLIN-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4834: Description: Hi. I'm yoonsung.lee developing & operating the statistical storage using Kylin in LINE Advertising dept. h1. Current Situation I understand there is only one active leader job server instance in a Kylin cluster. The leader job server is selected by Zookeeper if there are multiple active job servers in a Kylin cluster. This is my pain point. When my leader job server has a fault or shutdown, I want to change the leader job server automatically and the DNS server route the traffic to the changed one. In this case, I should know which one is the leader job server as soon as possible the leader(active) has changed. For this one, I try to watch the path of Zookeeper in which the Kylin server maintains the server list in a cluster. But, this approach has a fault in essence. It's not an implementation controlled by Kylin. h1. Question Is my approach appropriate for the Kylin cluster? If not, is there any better idea for fault tolerance of job servers with auto DNS or LoadBalancer mapping? h1. Suggestion So, I suggest this idea. Any server in a Kylin cluster forwards the API request to the leader job server in the case that the request should be done by the job server and pass valid authentication. If then, I just attach all of the servers to my LoadBalancer without caring about which one is the leader job server. * Could this feature be harmful or have side-effects? was: Hi. I'm yoonsung.lee developing & operating the statistical storage using Kylin in LINE Advertising dept. h1. Current Situation I understand there is only one active(leader) job server instance in a Kylin cluster. The active job server is selected by Zookeeper if there are multiple job servers in a Kylin cluster. This is my pain point. When my leader job server has a fault or shutdown, I want to change the leader job server automatically and the DNS server route the traffic to the changed one. In this case, I should know which one is the leader job server as soon as possible the leader(active) has changed. For this one, I try to watch the path of zookeeper in which the Kylin server maintain the server list in a cluster. But, this approach has a fault in essence. It's not an implementation controlled by Kylin. h1. Question Is my approach appropriate for the Kylin cluster? If not, is there any better idea for fault tolerance of job servers with auto DNS or LoadBalancer mapping? h1. Suggestion So, I suggest this idea. Any server in a Kylin cluster forwards the API request to the leader job server in the case that the request should be done by the job server and pass valid authentication. If then, I just attach all of the servers to my LoadBalancer without caring about which one is the leader job server. * Could this feature be harmful or have side-effects? > Auto forward the job API request to the available leader job server > --- > > Key: KYLIN-4834 > URL: https://issues.apache.org/jira/browse/KYLIN-4834 > Project: Kylin > Issue Type: Wish > Components: Others >Reporter: yoonsung.lee >Priority: Minor > > Hi. I'm yoonsung.lee developing & operating the statistical storage using > Kylin in LINE Advertising dept. > h1. Current Situation > I understand there is only one active leader job server instance in a Kylin > cluster. > The leader job server is selected by Zookeeper if there are multiple active > job servers in a Kylin cluster. > This is my pain point. > When my leader job server has a fault or shutdown, I want to change the > leader job server automatically and the DNS server route the traffic to the > changed one. > In this case, I should know which one is the leader job server as soon as > possible the leader(active) has changed. > For this one, I try to watch the path of Zookeeper in which the Kylin server > maintains the server list in a cluster. > But, this approach has a fault in essence. It's not an implementation > controlled by Kylin. > h1. Question > Is my approach appropriate for the Kylin cluster? > If not, is there any better idea for fault tolerance of job servers with auto > DNS or LoadBalancer mapping? > h1. Suggestion > So, I suggest this idea. > Any server in a Kylin cluster forwards the API request to the leader job > server in the case that the request should be done by the job server and pass > valid authentication. If then, I just attach all of the servers to my > LoadBalancer without caring about which one is the leader job server. > * Could this feature be harmful or have side-effects? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4834) Auto forward the job API request to the available leader job server
yoonsung.lee created KYLIN-4834: --- Summary: Auto forward the job API request to the available leader job server Key: KYLIN-4834 URL: https://issues.apache.org/jira/browse/KYLIN-4834 Project: Kylin Issue Type: Wish Components: Others Reporter: yoonsung.lee Hi. I'm yoonsung.lee developing & operating the statistical storage using Kylin in LINE Advertising dept. h1. Current Situation I understand there is only one active(leader) job server instance in a Kylin cluster. The active job server is selected by Zookeeper if there are multiple job servers in a Kylin cluster. This is my pain point. When my leader job server has a fault or shutdown, I want to change the leader job server automatically and the DNS server route the traffic to the changed one. In this case, I should know which one is the leader job server as soon as possible the leader(active) has changed. For this one, I try to watch the path of zookeeper in which the Kylin server maintain the server list in a cluster. But, this approach has a fault in essence. It's not an implementation controlled by Kylin. h1. Question Is my approach appropriate for the Kylin cluster? If not, is there any better idea for fault tolerance of job servers with auto DNS or LoadBalancer mapping? h1. Suggestion So, I suggest this idea. Any server in a Kylin cluster forwards the API request to the leader job server in the case that the request should be done by the job server and pass valid authentication. If then, I just attach all of the servers to my LoadBalancer without caring about which one is the leader job server. * Could this feature be harmful or have side-effects? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4809) Support maven wrapper
[ https://issues.apache.org/jira/browse/KYLIN-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4809: Description: Hi. This project uses maven. I want to introduce a build supporting tool, [maven wrapper|https://github.com/takari/maven-wrapper]. It looks like the gradle wrapper which makes a project build anywhere without installing Gradle. It makes a project build anywhere without installing Maven. This feature has been recognized. The spring projects have been used actively. It will be added to the official feature of maven from 3.7.0, but the release date is not yet to be expected. (https://maven.apache.org/plugins/maven-wrapper-plugin/) If you agree with applying this tool to this project, please assign this task to me. I will make a PR for it. was: Hi. This project uses maven. I want to introduce a build supporting tool, [maven wrapper|https://github.com/takari/maven-wrapper]. It looks like the gradle wrapper which makes a project build anywhere without installing Gradle. It makes a project build anywhere without installing Maven. This feature has been recognized. The spring projects have been used actively. It will be added to the official feature of maven from 3.7.0, but the release date is not yet to be expected. If you agree with applying this tool to this project, please assign this task to me. I will make a PR for it. > Support maven wrapper > - > > Key: KYLIN-4809 > URL: https://issues.apache.org/jira/browse/KYLIN-4809 > Project: Kylin > Issue Type: Improvement > Components: Tools, Build and Test >Reporter: yoonsung.lee >Priority: Trivial > Fix For: all > > > Hi. This project uses maven. > I want to introduce a build supporting tool, [maven > wrapper|https://github.com/takari/maven-wrapper]. > It looks like the gradle wrapper which makes a project build anywhere without > installing Gradle. > It makes a project build anywhere without installing Maven. > This feature has been recognized. The spring projects have been used > actively. It will be added to the official feature of maven from 3.7.0, but > the release date is not yet to be expected. > (https://maven.apache.org/plugins/maven-wrapper-plugin/) > If you agree with applying this tool to this project, please assign this task > to me. I will make a PR for it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4809) Support maven wrapper
[ https://issues.apache.org/jira/browse/KYLIN-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4809: Description: Hi. This project uses maven. I want to introduce a build supporting tool, [maven wrapper|https://github.com/takari/maven-wrapper]. It looks like the gradle wrapper which makes a project build anywhere without installing Gradle. It makes a project build anywhere without installing Maven. This feature has been recognized. The spring projects have been used actively. It will be added to the official feature of maven from 3.7.0, but the release date is not yet to be expected. If you agree with applying this tool to this project, please assign this task to me. I will make a PR for it. was: Hi. This project uses maven. I want to introduce a build supporting tool, [maven wrapper|https://github.com/takari/maven-wrapper]. It looks like the gradle wrapper which makes a project build anywhere without installing Gradle. It makes a project build anywhere without installing Maven. This feature has been recognized. The spring projects have been used actively. It will be added to the official feature of maven from 3.7.0, but the release date is not yet to be expected. If you agree with applying this tool to this project, I will make a PR for it. > Support maven wrapper > - > > Key: KYLIN-4809 > URL: https://issues.apache.org/jira/browse/KYLIN-4809 > Project: Kylin > Issue Type: Improvement > Components: Tools, Build and Test >Reporter: yoonsung.lee >Priority: Trivial > Fix For: all > > > Hi. This project uses maven. > I want to introduce a build supporting tool, [maven > wrapper|https://github.com/takari/maven-wrapper]. > It looks like the gradle wrapper which makes a project build anywhere without > installing Gradle. > It makes a project build anywhere without installing Maven. > This feature has been recognized. The spring projects have been used > actively. It will be added to the official feature of maven from 3.7.0, but > the release date is not yet to be expected. > If you agree with applying this tool to this project, please assign this task > to me. I will make a PR for it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4809) Support maven wrapper
yoonsung.lee created KYLIN-4809: --- Summary: Support maven wrapper Key: KYLIN-4809 URL: https://issues.apache.org/jira/browse/KYLIN-4809 Project: Kylin Issue Type: Improvement Components: Tools, Build and Test Reporter: yoonsung.lee Fix For: all Hi. This project uses maven. I want to introduce a build supporting tool, [maven wrapper|https://github.com/takari/maven-wrapper]. It looks like the gradle wrapper which makes a project build anywhere without installing Gradle. It makes a project build anywhere without installing Maven. This feature has been recognized. The spring projects have been used actively. It will be added to the official feature of maven from 3.7.0, but the release date is not yet to be expected. If you agree with applying this tool to this project, I will make a PR for it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (KYLIN-4799) Let me know contribution guide
[ https://issues.apache.org/jira/browse/KYLIN-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee closed KYLIN-4799. --- > Let me know contribution guide > -- > > Key: KYLIN-4799 > URL: https://issues.apache.org/jira/browse/KYLIN-4799 > Project: Kylin > Issue Type: Improvement >Reporter: yoonsung.lee >Priority: Trivial > Labels: documentation > Fix For: all > > > Hi. I'm preparing to solve some issues that I'm interested in. > I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. > > Please let me know. If there doesn't exist, please consider making it to > invigorate this project. The contribution guide will make the code of this > project reliable and reduce communication costs. > > The followings are some properties that I expect it in the contribution guide. > * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. > * Copyright header. > * Guide for null check in Java. > * Guide for access modifier in Java > * Guide to organize code in a java class. > * Guide for the message of exception or log. > * Guide for write Javadoc when creating a class. > * Rest API convention. > * etc... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (KYLIN-4799) Let me know contribution guide
[ https://issues.apache.org/jira/browse/KYLIN-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee resolved KYLIN-4799. - Fix Version/s: all Reviewers: Shao Feng Shi Resolution: Fixed merged on https://github.com/apache/kylin/pull/1466 > Let me know contribution guide > -- > > Key: KYLIN-4799 > URL: https://issues.apache.org/jira/browse/KYLIN-4799 > Project: Kylin > Issue Type: Improvement >Reporter: yoonsung.lee >Priority: Trivial > Labels: documentation > Fix For: all > > > Hi. I'm preparing to solve some issues that I'm interested in. > I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. > > Please let me know. If there doesn't exist, please consider making it to > invigorate this project. The contribution guide will make the code of this > project reliable and reduce communication costs. > > The followings are some properties that I expect it in the contribution guide. > * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. > * Copyright header. > * Guide for null check in Java. > * Guide for access modifier in Java > * Guide to organize code in a java class. > * Guide for the message of exception or log. > * Guide for write Javadoc when creating a class. > * Rest API convention. > * etc... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4799) Let me know contribution guide
[ https://issues.apache.org/jira/browse/KYLIN-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4799: Issue Type: Improvement (was: Wish) > Let me know contribution guide > -- > > Key: KYLIN-4799 > URL: https://issues.apache.org/jira/browse/KYLIN-4799 > Project: Kylin > Issue Type: Improvement >Reporter: yoonsung.lee >Priority: Trivial > Labels: documentation > > Hi. I'm preparing to solve some issues that I'm interested in. > I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. > > Please let me know. If there doesn't exist, please consider making it to > invigorate this project. The contribution guide will make the code of this > project reliable and reduce communication costs. > > The followings are some properties that I expect it in the contribution guide. > * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. > * Copyright header. > * Guide for null check in Java. > * Guide for access modifier in Java > * Guide to organize code in a java class. > * Guide for the message of exception or log. > * Guide for write Javadoc when creating a class. > * Rest API convention. > * etc... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (KYLIN-4798) Let me know "good first issue" for contribution
[ https://issues.apache.org/jira/browse/KYLIN-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee closed KYLIN-4798. --- Resolution: Fixed It is already labeled as "newbie". > Let me know "good first issue" for contribution > --- > > Key: KYLIN-4798 > URL: https://issues.apache.org/jira/browse/KYLIN-4798 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > > Hi. I'm yoonsung.lee. > I set up and applied a Kylin cluster to the OLAP service in my company. > Thanks for your efforts during the last few years and make this awesome > product. > > I want to contribute to this project beyond just using it. > I've looked up the official website, documents, cwiki and this Jira tickets > for last 2 weeks. > It seems that you guys manage this project as this Jira ticket system, not a > public Github repository. > In this community, it is hard to understand which issue is a good first issue > for a newbie in this project. I've found out a good first issue as a label > "good first issue" from the other opensource project which is managed by the > Github issue system, like > [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. > > Where can I find the good first issues for newbies? > * suggestion: If there doesn't exist, how about creating a label named "good > first issue for contributing" and using it? > * I found "newbie*" labels in this Jira, but someone uses it as indicating > that the reporter is a newbie to this project. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-4799) Let me know contribution guide
[ https://issues.apache.org/jira/browse/KYLIN-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222671#comment-17222671 ] yoonsung.lee commented on KYLIN-4799: - Thanks [~shaofengshi]. Ok. I will make that PR and refer to the existing document. > Let me know contribution guide > -- > > Key: KYLIN-4799 > URL: https://issues.apache.org/jira/browse/KYLIN-4799 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > Labels: documentation > > Hi. I'm preparing to solve some issues that I'm interested in. > I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. > > Please let me know. If there doesn't exist, please consider making it to > invigorate this project. The contribution guide will make the code of this > project reliable and reduce communication costs. > > The followings are some properties that I expect it in the contribution guide. > * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. > * Copyright header. > * Guide for null check in Java. > * Guide for access modifier in Java > * Guide to organize code in a java class. > * Guide for the message of exception or log. > * Guide for write Javadoc when creating a class. > * Rest API convention. > * etc... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4799) Let me know contribution guide
[ https://issues.apache.org/jira/browse/KYLIN-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4799: Description: Hi. I'm preparing to solve some issues that I'm interested in. I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. Please let me know. If there doesn't exist, please consider to make it to invigorate this project. The followings are some properties that I expect it in the contribution guide. * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. * Copyright header. * Guide for null check in Java. * Guide for access modifier in Java * Guide to organize code in a java class. * Guide for the message of exception or log. * Guide for write Javadoc when creating a class. * Rest API convention. * etc... was: Hi. I'm preparing to solve some issues that I'm interested in. I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. Please let me know. If there doesn't exist, please consider to make it to invigorate this project. The followings are some properties that I expect it in the contribution guide. * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. * Copyright header. * Guide for null check in Java. * Guide for access modifier in Java * Guide to organize code in a java class. * Guide for exception message. * Guide for Javadoc. > Let me know contribution guide > -- > > Key: KYLIN-4799 > URL: https://issues.apache.org/jira/browse/KYLIN-4799 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > Labels: documentation > > Hi. I'm preparing to solve some issues that I'm interested in. > I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. > > Please let me know. If there doesn't exist, please consider to make it to > invigorate this project. > > The followings are some properties that I expect it in the contribution guide. > * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. > * Copyright header. > * Guide for null check in Java. > * Guide for access modifier in Java > * Guide to organize code in a java class. > * Guide for the message of exception or log. > * Guide for write Javadoc when creating a class. > * Rest API convention. > * etc... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4799) Let me know contribution guide
[ https://issues.apache.org/jira/browse/KYLIN-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4799: Description: Hi. I'm preparing to solve some issues that I'm interested in. I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. Please let me know. If there doesn't exist, please consider making it to invigorate this project. The contribution guide will make the code of this project reliable and reduce communication costs. The followings are some properties that I expect it in the contribution guide. * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. * Copyright header. * Guide for null check in Java. * Guide for access modifier in Java * Guide to organize code in a java class. * Guide for the message of exception or log. * Guide for write Javadoc when creating a class. * Rest API convention. * etc... was: Hi. I'm preparing to solve some issues that I'm interested in. I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. Please let me know. If there doesn't exist, please consider to make it to invigorate this project. The followings are some properties that I expect it in the contribution guide. * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. * Copyright header. * Guide for null check in Java. * Guide for access modifier in Java * Guide to organize code in a java class. * Guide for the message of exception or log. * Guide for write Javadoc when creating a class. * Rest API convention. * etc... > Let me know contribution guide > -- > > Key: KYLIN-4799 > URL: https://issues.apache.org/jira/browse/KYLIN-4799 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > Labels: documentation > > Hi. I'm preparing to solve some issues that I'm interested in. > I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. > > Please let me know. If there doesn't exist, please consider making it to > invigorate this project. The contribution guide will make the code of this > project reliable and reduce communication costs. > > The followings are some properties that I expect it in the contribution guide. > * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. > * Copyright header. > * Guide for null check in Java. > * Guide for access modifier in Java > * Guide to organize code in a java class. > * Guide for the message of exception or log. > * Guide for write Javadoc when creating a class. > * Rest API convention. > * etc... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4799) Let me know contribution guide
[ https://issues.apache.org/jira/browse/KYLIN-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4799: Description: Hi. I'm preparing to solve some issues that I'm interested in. I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. Please let me know. If there doesn't exist, please consider to make it to invigorate this project. The followings are some properties that I expect it in the contribution guide. * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. * Copyright header. * Guide for null check in Java. * Guide for access modifier in Java * Guide to organize code in a java class. * Guide for exception message. * Guide for Javadoc. was: Hi. I'm preparing to solve some issues that I'm interested in. I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. Please let me know. If there doesn't exist, please consider to make it to invigorate this project. > Let me know contribution guide > -- > > Key: KYLIN-4799 > URL: https://issues.apache.org/jira/browse/KYLIN-4799 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > Labels: documentation > > Hi. I'm preparing to solve some issues that I'm interested in. > I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. > > Please let me know. If there doesn't exist, please consider to make it to > invigorate this project. > > The followings are some properties that I expect it in the contribution guide. > * Code style schema for IDE such as IntelliJ, vscode, vim, and etc. > * Copyright header. > * Guide for null check in Java. > * Guide for access modifier in Java > * Guide to organize code in a java class. > * Guide for exception message. > * Guide for Javadoc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4798) Let me know "good first issue" for contribution
[ https://issues.apache.org/jira/browse/KYLIN-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4798: Summary: Let me know "good first issue" for contribution (was: Let me know "good first issue") > Let me know "good first issue" for contribution > --- > > Key: KYLIN-4798 > URL: https://issues.apache.org/jira/browse/KYLIN-4798 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > > Hi. I'm yoonsung.lee. > I set up and applied a Kylin cluster to the OLAP service in my company. > Thanks for your efforts during the last few years and make this awesome > product. > > I want to contribute to this project beyond just using it. > I've looked up the official website, documents, cwiki and this Jira tickets > for last 2 weeks. > It seems that you guys manage this project as this Jira ticket system, not a > public Github repository. > In this community, it is hard to understand which issue is a good first issue > for a newbie in this project. I've found out a good first issue as a label > "good first issue" from the other opensource project which is managed by the > Github issue system, like > [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. > > Where can I find the good first issues for newbies? > * suggestion: If there doesn't exist, how about creating a label named "good > first issue for contributing" and using it? > * I found "newbie*" labels in this Jira, but someone uses it as indicating > that the reporter is a newbie to this project. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4798) Let me know "good first issue"
[ https://issues.apache.org/jira/browse/KYLIN-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4798: Description: Hi. I'm yoonsung.lee. I set up and applied a Kylin cluster to the OLAP service in my company. Thanks for your efforts during the last few years and make this awesome product. I want to contribute to this project beyond just using it. I've looked up the official website, documents, cwiki and this Jira tickets for last 2 weeks. It seems that you guys manage this project as this Jira ticket system, not a public Github repository. In this community, it is hard to understand which issue is a good first issue for a newbie in this project. I've found out a good first issue as a label "good first issue" from the other opensource project which is managed by the Github issue system, like [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. Where can I find the good first issues for newbies? * suggestion: If there doesn't exist, how about creating a label named "good first issue for contributing" and using it? * I found "newbie*" labels in this Jira, but someone uses it as indicating that the reporter is a newbie to this project. was: Hi. I'm yoonsung.lee. I set up and applied a Kylin cluster to the OLAP service in my company. Thanks for your efforts during the last few years and make this awesome product. I want to contribute to this project beyond just using it. I've looked up the official website, documents, cwiki and this Jira tickets for last 2 weeks. It seems that you guys manage this project as this Jira ticket system, not a public Github repository. In this community, it is hard to understand which issue is a good first issue for a newbie in this project. I've found out a good first issue as a label "good first issue" from the other opensource project which is managed by the Github issue system, like [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. Where can I find the good first issues for newbies? * suggestion: If there doesn't exist, how about creating a label named "good first issue for contributing" and using it? > Let me know "good first issue" > -- > > Key: KYLIN-4798 > URL: https://issues.apache.org/jira/browse/KYLIN-4798 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > > Hi. I'm yoonsung.lee. > I set up and applied a Kylin cluster to the OLAP service in my company. > Thanks for your efforts during the last few years and make this awesome > product. > > I want to contribute to this project beyond just using it. > I've looked up the official website, documents, cwiki and this Jira tickets > for last 2 weeks. > It seems that you guys manage this project as this Jira ticket system, not a > public Github repository. > In this community, it is hard to understand which issue is a good first issue > for a newbie in this project. I've found out a good first issue as a label > "good first issue" from the other opensource project which is managed by the > Github issue system, like > [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. > > Where can I find the good first issues for newbies? > * suggestion: If there doesn't exist, how about creating a label named "good > first issue for contributing" and using it? > * I found "newbie*" labels in this Jira, but someone uses it as indicating > that the reporter is a newbie to this project. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KYLIN-4798) Let me know "good first issue"
[ https://issues.apache.org/jira/browse/KYLIN-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yoonsung.lee updated KYLIN-4798: Description: Hi. I'm yoonsung.lee. I set up and applied a Kylin cluster to the OLAP service in my company. Thanks for your efforts during the last few years and make this awesome product. I want to contribute to this project beyond just using it. I've looked up the official website, documents, cwiki and this Jira tickets for last 2 weeks. It seems that you guys manage this project as this Jira ticket system, not a public Github repository. In this community, it is hard to understand which issue is a good first issue for a newbie in this project. I've found out a good first issue as a label "good first issue" from the other opensource project which is managed by the Github issue system, like [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. Where can I find the good first issues for newbies? * suggestion: If there doesn't exist, how about creating a label named "good first issue for contributing" and using it? was: Hi. I'm yoonsung.lee. I set up and applied a Kylin cluster to the OLAP service in my company. Thanks for your efforts during the last few years and make this awesome product. I want to contribute to this project beyond just using it. I've looked up the official website, documents, cwiki and this Jira tickets for last 2 weeks. It seems that you guys manage this project as this Jira ticket system, not a public Github repository. In this community, it is hard to understand which issue is a good first issue for a newbie in this project. I've found out a good first issue as a label "good first issue" from the other opensource project which is managed by the Github issue system, like [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. Where can I find the good first issues for newbies? * suggestion: If there doesn't exist, how about creating a label named "good first issue" and using it? > Let me know "good first issue" > -- > > Key: KYLIN-4798 > URL: https://issues.apache.org/jira/browse/KYLIN-4798 > Project: Kylin > Issue Type: Wish >Reporter: yoonsung.lee >Priority: Trivial > > Hi. I'm yoonsung.lee. > I set up and applied a Kylin cluster to the OLAP service in my company. > Thanks for your efforts during the last few years and make this awesome > product. > > I want to contribute to this project beyond just using it. > I've looked up the official website, documents, cwiki and this Jira tickets > for last 2 weeks. > It seems that you guys manage this project as this Jira ticket system, not a > public Github repository. > In this community, it is hard to understand which issue is a good first issue > for a newbie in this project. I've found out a good first issue as a label > "good first issue" from the other opensource project which is managed by the > Github issue system, like > [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. > > Where can I find the good first issues for newbies? > * suggestion: If there doesn't exist, how about creating a label named "good > first issue for contributing" and using it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4799) Let me know contribution guide
yoonsung.lee created KYLIN-4799: --- Summary: Let me know contribution guide Key: KYLIN-4799 URL: https://issues.apache.org/jira/browse/KYLIN-4799 Project: Kylin Issue Type: Wish Reporter: yoonsung.lee Hi. I'm preparing to solve some issues that I'm interested in. I cannot find CONTRIBUTING.md and CODE_OF_CONDUCT.md in the Github repository. Please let me know. If there doesn't exist, please consider to make it to invigorate this project. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4798) Let me know "good first issue"
yoonsung.lee created KYLIN-4798: --- Summary: Let me know "good first issue" Key: KYLIN-4798 URL: https://issues.apache.org/jira/browse/KYLIN-4798 Project: Kylin Issue Type: Wish Reporter: yoonsung.lee Hi. I'm yoonsung.lee. I set up and applied a Kylin cluster to the OLAP service in my company. Thanks for your efforts during the last few years and make this awesome product. I want to contribute to this project beyond just using it. I've looked up the official website, documents, cwiki and this Jira tickets for last 2 weeks. It seems that you guys manage this project as this Jira ticket system, not a public Github repository. In this community, it is hard to understand which issue is a good first issue for a newbie in this project. I've found out a good first issue as a label "good first issue" from the other opensource project which is managed by the Github issue system, like [this|https://github.com/line/armeria/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22]. Where can I find the good first issues for newbies? * suggestion: If there doesn't exist, how about creating a label named "good first issue" and using it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
