Re: No of arguments passing issue in kylin query
forgot to add 2nd query.
SELECT AL_PROD.CLNDR_DT, AL_PROD.TRIP_NAME, AL_PROD.ROUTE_NAME,
AL_PROD.DRIVER_NAME,AL_PROD.TOT_DIS_COV, AL_PROD.REGN_NUMBER FROM (SELECT
AL_TIME_DIM.CLNDR_DT,AL_TIME_DIM.CLNDR_DT,AL_PROD_RPT_FACT.VEHICLE_KEY,AL_DRIVER_DIM.DRIVER_ID,AL_TRIP_DIM.TRIP_NAME,AL_TRIP_DIM.TRIP_ID,AL_ROUTE_DIM.ROUTE_NAME,AL_ROUTE_DIM.ROUTE_ID,AL_DRIVER_DIM.FIRST_NAME
|| ' ' || AL_DRIVER_DIM.LAST_NAME AS
DRIVER_NAME,AL_PROD_RPT_FACT.TOT_DIS_COV,AL_VEHICLE_DIM.REGN_NUMBER FROM
AL_PROD.AL_PROD_RPT_FACT AL_PROD_RPT_FACT inner join AL_PROD.AL_TRIP_DIM
AL_TRIP_DIM on AL_PROD_RPT_FACT.TRIP_KEY=AL_TRIP_DIM.TRIP_KEY inner join
AL_PROD.AL_ROUTE_DIM AL_ROUTE_DIM on
AL_PROD_RPT_FACT.ROUTE_KEY=AL_ROUTE_DIM.ROUTE_KEY inner join
AL_PROD.AL_DRIVER_DIM AL_DRIVER_DIM on
AL_PROD_RPT_FACT.DRIVER_KEY=AL_DRIVER_DIM.DRIVER_KEY inner join
AL_PROD.AL_VEHICLE_DIM AL_VEHICLE_DIM on
AL_PROD_RPT_FACT.VEHICLE_KEY=AL_VEHICLE_DIM.VEHICLE_KEY inner join
AL_PROD.AL_TIME_DIM AL_TIME_DIM on
AL_PROD_RPT_FACT.TIME_KEY=AL_TIME_DIM.TIM_ID where
AL_VEHICLE_DIM.EFF_TO_DATE= date '-12-30') AL_PROD where
AL_PROD.REGN_NUMBER in ('TN18 AH4772') and AL_PROD.TRIP_ID in
(274,278,288,293,298,303) and AL_PROD.CLNDR_DT BETWEEN '2017-06-20' and
'2017-06-20' order by AL_PROD.CLNDR_DT
On Thu, Jun 22, 2017 at 2:45 PM, suresh m <suresh.m8...@gmail.com> wrote:
> Hi,
>
> Facing an issue with passing no of arguments in Kylin Query.
>
> When I am querying with less than or eaqual to 5 arguements result is
> coming properly. If i pass more than 5 arguments result showing as 0 even
> though records there in cube.
>
> sending you the query as well,
>
>
> SELECT AL_PROD.CLNDR_DT, AL_PROD.TRIP_NAME, AL_PROD.ROUTE_NAME,
> AL_PROD.DRIVER_NAME,AL_PROD.TOT_DIS_COV, AL_PROD.REGN_NUMBER FROM (SELECT
> AL_TIME_DIM.CLNDR_DT,AL_TIME_DIM.CLNDR_DT,AL_PROD_RPT_FACT.
> VEHICLE_KEY,AL_DRIVER_DIM.DRIVER_ID,AL_TRIP_DIM.TRIP_
> NAME,AL_TRIP_DIM.TRIP_ID,AL_ROUTE_DIM.ROUTE_NAME,AL_ROUTE_
> DIM.ROUTE_ID,AL_DRIVER_DIM.FIRST_NAME || ' ' || AL_DRIVER_DIM.LAST_NAME
> AS DRIVER_NAME,AL_PROD_RPT_FACT.TOT_DIS_COV,AL_VEHICLE_DIM.REGN_NUMBER
> FROM AL_PROD.AL_PROD_RPT_FACT AL_PROD_RPT_FACT inner join
> AL_PROD.AL_TRIP_DIM AL_TRIP_DIM on
> AL_PROD_RPT_FACT.TRIP_KEY=AL_TRIP_DIM.TRIP_KEY
> inner join AL_PROD.AL_ROUTE_DIM AL_ROUTE_DIM on
> AL_PROD_RPT_FACT.ROUTE_KEY=AL_ROUTE_DIM.ROUTE_KEY inner join
> AL_PROD.AL_DRIVER_DIM AL_DRIVER_DIM on
> AL_PROD_RPT_FACT.DRIVER_KEY=AL_DRIVER_DIM.DRIVER_KEY
> inner join AL_PROD.AL_VEHICLE_DIM AL_VEHICLE_DIM on
> AL_PROD_RPT_FACT.VEHICLE_KEY=AL_VEHICLE_DIM.VEHICLE_KEY inner join
> AL_PROD.AL_TIME_DIM AL_TIME_DIM on
> AL_PROD_RPT_FACT.TIME_KEY=AL_TIME_DIM.TIM_ID
> where AL_VEHICLE_DIM.EFF_TO_DATE= date '-12-30') AL_PROD where
> AL_PROD.REGN_NUMBER in ('TN18 AH4772') and AL_PROD.TRIP_ID in
> (278,288,293,298,303) and AL_PROD.CLNDR_DT BETWEEN '2017-06-20' and
> '2017-06-20' order by AL_PROD.CLNDR_DT;
>
>
> in above query we can see only 5 arguments passing for trip_id. For this
> query result is coming properly and it showing 5 trips as well.
>
> But in below query passing 6 trip id's then result is showing as 0 trips
> and if i removed 1 trip id from the list then its showing 5 trips as usual.
>
>
>
> let me know is there any limitation of passing arguments. If yes let me
> know how resolve this.
>
>
>
> Regards,
>
> Suresh
>
>
>
No of arguments passing issue in kylin query
Hi,
Facing an issue with passing no of arguments in Kylin Query.
When I am querying with less than or eaqual to 5 arguements result is
coming properly. If i pass more than 5 arguments result showing as 0 even
though records there in cube.
sending you the query as well,
SELECT AL_PROD.CLNDR_DT, AL_PROD.TRIP_NAME, AL_PROD.ROUTE_NAME,
AL_PROD.DRIVER_NAME,AL_PROD.TOT_DIS_COV, AL_PROD.REGN_NUMBER FROM (SELECT
AL_TIME_DIM.CLNDR_DT,AL_TIME_DIM.CLNDR_DT,AL_PROD_RPT_FACT.VEHICLE_KEY,AL_DRIVER_DIM.DRIVER_ID,AL_TRIP_DIM.TRIP_NAME,AL_TRIP_DIM.TRIP_ID,AL_ROUTE_DIM.ROUTE_NAME,AL_ROUTE_DIM.ROUTE_ID,AL_DRIVER_DIM.FIRST_NAME
|| ' ' || AL_DRIVER_DIM.LAST_NAME AS
DRIVER_NAME,AL_PROD_RPT_FACT.TOT_DIS_COV,AL_VEHICLE_DIM.REGN_NUMBER FROM
AL_PROD.AL_PROD_RPT_FACT AL_PROD_RPT_FACT inner join AL_PROD.AL_TRIP_DIM
AL_TRIP_DIM on AL_PROD_RPT_FACT.TRIP_KEY=AL_TRIP_DIM.TRIP_KEY inner join
AL_PROD.AL_ROUTE_DIM AL_ROUTE_DIM on
AL_PROD_RPT_FACT.ROUTE_KEY=AL_ROUTE_DIM.ROUTE_KEY inner join
AL_PROD.AL_DRIVER_DIM AL_DRIVER_DIM on
AL_PROD_RPT_FACT.DRIVER_KEY=AL_DRIVER_DIM.DRIVER_KEY inner join
AL_PROD.AL_VEHICLE_DIM AL_VEHICLE_DIM on
AL_PROD_RPT_FACT.VEHICLE_KEY=AL_VEHICLE_DIM.VEHICLE_KEY inner join
AL_PROD.AL_TIME_DIM AL_TIME_DIM on
AL_PROD_RPT_FACT.TIME_KEY=AL_TIME_DIM.TIM_ID where
AL_VEHICLE_DIM.EFF_TO_DATE= date '-12-30') AL_PROD where
AL_PROD.REGN_NUMBER in ('TN18 AH4772') and AL_PROD.TRIP_ID in
(278,288,293,298,303) and AL_PROD.CLNDR_DT BETWEEN '2017-06-20' and
'2017-06-20' order by AL_PROD.CLNDR_DT;
in above query we can see only 5 arguments passing for trip_id. For this
query result is coming properly and it showing 5 trips as well.
But in below query passing 6 trip id's then result is showing as 0 trips
and if i removed 1 trip id from the list then its showing 5 trips as usual.
let me know is there any limitation of passing arguments. If yes let me
know how resolve this.
Regards,
Suresh
How to change kylin execution engine from Mapreduce to Tez
Hi, I can see here my kylin job executing threw Mapreduce, i think this is one of the reason for taking more time to build cube. Is there any chance to change execution engine as Tez. Attaching screen shot for reference.
cube building with huge memory, for 5000 records 2.3GB
Hi, My kylin cube taking huge memory just for few records. Even i changed compression property as Snappy but still occupying huge memory. Attaching screenshot for your reference. Suggestions are welcome to reduce cube size. Regards, Suresh
Re: cube building taking 8 hours just for 6 thousands records
Hi Thanks for your timely reply. I set kylin.cube.algorithm=layer , but still facing same issue. Please let me know any other tuning to improve performance. Regards, Suresh On Tue, Apr 18, 2017 at 7:23 PM, Li Yang <liy...@apache.org> wrote: > > #24 Step Name: Build Cube > > It is in-mem cubing taking effect and seems it does not fit your cluster. > Try set below in kylin.properties to use layer cubing instead. > > kylin.cube.algorithm=layer > > > Cheers > Yang > > On Tue, Apr 18, 2017 at 9:13 PM, Alberto Ramón <a.ramonporto...@gmail.com> > wrote: > > > Is this your configuration? (check this properties): > > > >- > > > >yarn.nodemanager.resource.memory-mb =150/3 > >- > > > >yarn.nodemanager.resource.cpu-vcores= 36/3 > > > > And Check the YARN UI, during build phase (you can see how many Mappers > and > > reduce, RAM and CPU are you using) > > > > 2017-04-18 13:45 GMT+01:00 suresh m <suresh.m8...@gmail.com>: > > > > > sorry it is for all 3 nodes. > > > > > > each node 55gb ram and 12 cpu are there. > > > > > > On Tue, Apr 18, 2017 at 6:09 PM, Alberto Ramón < > > a.ramonporto...@gmail.com> > > > wrote: > > > > > > > Are these 150 GB and 36 CPUs configured in? > > > > > > > >- > > > > > > > >yarn.nodemanager.resource.memory-mb > > > >- > > > > > > > >yarn.nodemanager.resource.cpu-vcores > > > > > > > > During Build process, you can open YARN UI how many map-reduce are > you > > > > using. > > > > > > > > 2017-04-18 13:21 GMT+01:00 suresh m <suresh.m8...@gmail.com>: > > > > > > > > > Hi, > > > > > > > > > > I can see 150gb ram and 36 cpu in our cluster. > > > > > > > > > > On Tue, Apr 18, 2017 at 12:48 PM, Alberto Ramón < > > > > a.ramonporto...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > Can you check how many ram and cpu is asigned to yarn? > > > > > > > > > > > > El 18 abr. 2017 7:40 a. m., "suresh m" <suresh.m8...@gmail.com> > > > > > escribió: > > > > > > > > > > > > > Hi This is the time consuming step in entire build process. > > > > > > > > > > > > > > #24 Step Name: Build Cube > > > > > > > > > > > > > > Please help me to get it resolved. > > > > > > > > > > > > > > Regards, > > > > > > > Suresh > > > > > > > > > > > > > > On Mon, Apr 17, 2017 at 5:09 PM, 康凯森 <kangkai...@qq.com> > wrote: > > > > > > > > > > > > > > > what's the slowest step in your cube job? > > > > > > > > please refer to http://kylin.apache.org/ > > > > > docs20/howto/howto_optimize_ > > > > > > > > build.html > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- 原始邮件 -- > > > > > > > > 发件人: "suresh m";<suresh.m8...@gmail.com>; > > > > > > > > 发送时间: 2017年4月17日(星期一) 晚上7:05 > > > > > > > > 收件人: "dev"<dev@kylin.apache.org>; > > > > > > > > > > > > > > > > 主题: cube building taking 8 hours just for 6 thousands records > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > One of my cube taking hours to build even though its having > > less > > > > > > > > records(6000), please provide me some tuning techniques to > > > improve > > > > > > > > performance in Kylin. > > > > > > > > > > > > > > > > Regards. > > > > > > > > Suresh > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: cube building taking 8 hours just for 6 thousands records
sorry it is for all 3 nodes. each node 55gb ram and 12 cpu are there. On Tue, Apr 18, 2017 at 6:09 PM, Alberto Ramón <a.ramonporto...@gmail.com> wrote: > Are these 150 GB and 36 CPUs configured in? > >- > >yarn.nodemanager.resource.memory-mb >- > >yarn.nodemanager.resource.cpu-vcores > > During Build process, you can open YARN UI how many map-reduce are you > using. > > 2017-04-18 13:21 GMT+01:00 suresh m <suresh.m8...@gmail.com>: > > > Hi, > > > > I can see 150gb ram and 36 cpu in our cluster. > > > > On Tue, Apr 18, 2017 at 12:48 PM, Alberto Ramón < > a.ramonporto...@gmail.com > > > > > wrote: > > > > > Can you check how many ram and cpu is asigned to yarn? > > > > > > El 18 abr. 2017 7:40 a. m., "suresh m" <suresh.m8...@gmail.com> > > escribió: > > > > > > > Hi This is the time consuming step in entire build process. > > > > > > > > #24 Step Name: Build Cube > > > > > > > > Please help me to get it resolved. > > > > > > > > Regards, > > > > Suresh > > > > > > > > On Mon, Apr 17, 2017 at 5:09 PM, 康凯森 <kangkai...@qq.com> wrote: > > > > > > > > > what's the slowest step in your cube job? > > > > > please refer to http://kylin.apache.org/ > > docs20/howto/howto_optimize_ > > > > > build.html > > > > > > > > > > > > > > > > > > > > > > > > > -- 原始邮件 -- > > > > > 发件人: "suresh m";<suresh.m8...@gmail.com>; > > > > > 发送时间: 2017年4月17日(星期一) 晚上7:05 > > > > > 收件人: "dev"<dev@kylin.apache.org>; > > > > > > > > > > 主题: cube building taking 8 hours just for 6 thousands records > > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > One of my cube taking hours to build even though its having less > > > > > records(6000), please provide me some tuning techniques to improve > > > > > performance in Kylin. > > > > > > > > > > Regards. > > > > > Suresh > > > > > > > > > > > > > > >
Re: cube building taking 8 hours just for 6 thousands records
Hi This is the time consuming step in entire build process. #24 Step Name: Build Cube Please help me to get it resolved. Regards, Suresh On Mon, Apr 17, 2017 at 5:09 PM, 康凯森 <kangkai...@qq.com> wrote: > what's the slowest step in your cube job? > please refer to http://kylin.apache.org/docs20/howto/howto_optimize_ > build.html > > > > > -- 原始邮件 ------ > 发件人: "suresh m";<suresh.m8...@gmail.com>; > 发送时间: 2017年4月17日(星期一) 晚上7:05 > 收件人: "dev"<dev@kylin.apache.org>; > > 主题: cube building taking 8 hours just for 6 thousands records > > > > Hi All, > > One of my cube taking hours to build even though its having less > records(6000), please provide me some tuning techniques to improve > performance in Kylin. > > Regards. > Suresh >
Re: Is there any limitation of columns in Fact table in kylin
Hi Could you please respond on this very urgent for me. Regards, Suresh On Tue, Mar 28, 2017 at 7:13 AM, suresh m <suresh.m8...@gmail.com> wrote: > Hi, > > > One of my fact table contains 125 columns and while creating the cube > showing attached error. > > Please let me know, is there any limitation on columns and how to resolve > this issue. > > >
error while refreshing cube with curl script
Hi,
Please find the curl script what i am using for refreshing cube.
curl -u ADMIN:KYLIN -X PUT -H "Content-Type: application/json" -d
'{"startTime": 140479590,"endTime": 224061090,"buildType":
"REFRESH"}' http://*.*.*.*:7070/kylin/api/cubes/AL_RPT_PROD/rebuild
Getting below error when executing this script. But Same script is working
properly in Dev environment but facing issue in production.
{"url":"http://
*.*.*.*:7070/kylin/api/cubes/AL_RPT_PROD/rebuild","exception":null}
Please help me to solve this issue.
Regards,
Suresh
Re: Error while cube refreshing using REST API
Thanks for your timely reply.
I changed start date and end date as given in cube then its working fine.
On Wed, Mar 1, 2017 at 3:23 PM, Billy Liu <billy...@apache.org> wrote:
> It's not a bug, as the exception message is clear "NO match segment",
> please check your parameter and figure out which segment you were
> refreshing.
>
> One more thing, please do not open JIRA for questions.
>
> 2017-02-28 19:06 GMT+08:00 suresh m <suresh.m8...@gmail.com>:
>
> > Hi,
> >
> > Getting below error While refreshing cube with REST API.
> >
> > Request failed:
> > {"url":"http://*.*.*.*:7070/kylin/api/cubes/TEST/rebuild;,
> "exception":"The
> > new refreshing segment TEST[20170228105510_20170228115510] does not
> match
> > any existing segment in cube CUBE[name=TEST]"}
> >
> >
> > Please suggest solution to resolve this issue.
> >
> >
> > Regards,
> >
> > Suresh
> >
>
Urgent!!! exact sum of values are not coming in kylin when executed query in Insight
Hi, I am facing one issue where i need customised sum of values, but i can see there is a mismatch in actual sum and sum in kylin. and as i observed if there is repeated value its taking only once for summery. But in hive i can see exact result and only issue with kylin For ex: i have my data like below val date 5 1/12/2017 5 1/12/2017 2 1/12/2017 9 1/12/2017 1 1/13/2017 Actually sum of val group by date means it should give like below, sum date 21 1/12/2017 1 1/13/2017 But kylin when i execute sum query getting below result, sum date 16 1/12/2017 1 1/13/2017 We can see clearly its considering distinct values for summarizing result. Please help to resolve this asap Regards, Suresh
Re: Is kylin not support Hive ORC tables with ACID properties.
Please find detail as requested,
Log Type: syslog
Log Upload Time: Fri Nov 25 15:16:35 +0530 2016
Log Length: 107891
2016-11-25 15:15:35,185 INFO [main]
org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Created MRAppMaster
for application appattempt_1479580915733_0167_01
2016-11-25 15:15:35,592 WARN [main]
org.apache.hadoop.util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where
applicable
2016-11-25 15:15:35,630 INFO [main]
org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Executing with tokens:
2016-11-25 15:15:35,956 INFO [main]
org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Kind:
YARN_AM_RM_TOKEN, Service: , Ident: (appAttemptId { application_id {
id: 167 cluster_timestamp: 1479580915733 } attemptId: 1 } keyId:
2128280969)
2016-11-25 15:15:35,974 INFO [main]
org.apache.hadoop.mapreduce.v2.app.MRAppMaster: Using mapred
newApiCommitter.
2016-11-25 15:15:35,976 INFO [main]
org.apache.hadoop.mapreduce.v2.app.MRAppMaster: OutputCommitter set in
config null
2016-11-25 15:15:36,029 INFO [main]
org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter: File
Output Committer Algorithm version is 1
2016-11-25 15:15:36,029 INFO [main]
org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter:
FileOutputCommitter skip cleanup _temporary folders under output
directory:false, ignore cleanup failures: false
2016-11-25 15:15:36,692 WARN [main]
org.apache.hadoop.hdfs.shortcircuit.DomainSocketFactory: The
short-circuit local reads feature cannot be used because libhadoop
cannot be loaded.
2016-11-25 15:15:36,702 INFO [main]
org.apache.hadoop.mapreduce.v2.app.MRAppMaster: OutputCommitter is
org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter
2016-11-25 15:15:36,891 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.jobhistory.EventType for class
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler
2016-11-25 15:15:36,891 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.job.event.JobEventType for class
org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobEventDispatcher
2016-11-25 15:15:36,892 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.job.event.TaskEventType for class
org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskEventDispatcher
2016-11-25 15:15:36,893 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.job.event.TaskAttemptEventType for
class org.apache.hadoop.mapreduce.v2.app.MRAppMaster$TaskAttemptEventDispatcher
2016-11-25 15:15:36,893 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventType for class
org.apache.hadoop.mapreduce.v2.app.commit.CommitterEventHandler
2016-11-25 15:15:36,894 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.speculate.Speculator$EventType for
class org.apache.hadoop.mapreduce.v2.app.MRAppMaster$SpeculatorEventDispatcher
2016-11-25 15:15:36,894 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.rm.ContainerAllocator$EventType for
class org.apache.hadoop.mapreduce.v2.app.MRAppMaster$ContainerAllocatorRouter
2016-11-25 15:15:36,895 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.launcher.ContainerLauncher$EventType
for class org.apache.hadoop.mapreduce.v2.app.MRAppMaster$ContainerLauncherRouter
2016-11-25 15:15:36,923 INFO [main]
org.apache.hadoop.mapreduce.v2.jobhistory.JobHistoryUtils: Default
file system is set solely by core-default.xml therefore - ignoring
2016-11-25 15:15:36,945 INFO [main]
org.apache.hadoop.mapreduce.v2.jobhistory.JobHistoryUtils: Default
file system is set solely by core-default.xml therefore - ignoring
2016-11-25 15:15:36,967 INFO [main]
org.apache.hadoop.mapreduce.v2.jobhistory.JobHistoryUtils: Default
file system is set solely by core-default.xml therefore - ignoring
2016-11-25 15:15:37,029 INFO [main]
org.apache.hadoop.mapreduce.jobhistory.JobHistoryEventHandler:
Emitting job history data to the timeline server is not enabled
2016-11-25 15:15:37,064 INFO [main]
org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class
org.apache.hadoop.mapreduce.v2.app.job.event.JobFinishEvent$Type for
class org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobFinishEventHandler
2016-11-25 15:15:37,204 WARN [main]
org.apache.hadoop.metrics2.impl.MetricsConfig: Cannot locate
configuration: tried
hadoop-metrics2-mrappmaster.properties,hadoop-metrics2.properties
2016-11-25 15:15:37,300 INFO [main]
org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot
period at 10 second(s).
2016-11-25 15:15:37,300 INFO [main]
org.apache.hadoop.metrics2.impl.MetricsSystemImpl: MRAppMaster metrics
Re: how to refresh cube automatically in kylin 1.5.4.1
Thanks Alberto, Its really helped me lot. On Thu, Nov 10, 2016 at 1:27 PM, Alberto Ramón <a.ramonporto...@gmail.com> wrote: > You have 2 options: > SOL1: Rest Full API > <http://kylin.apache.org/docs15/howto/howto_use_restapi.html> See this > example > <https://kylin.apache.org/docs15/howto/howto_use_restapi.html#build-cube> > SOL2: Kylin Client Tool > <http://kylin.apache.org/docs/tutorial/kylin_client_tool.html> with Python > + Cron + Curl Command > > See this previous mailList from Shi: > http://mail-archives.apache.org/mod_mbox/kylin-user/ > 201607.mbox/%3CCAF7etTns%3DO%2BA5iN9vB8BGxGM6HQT- > EieUiqGh3msTm9zaEaUiQ%40mail.gmail.com%3E > > 2016-11-10 7:53 GMT+01:00 suresh m <suresh.m8...@gmail.com>: > > > Hi, > > > > I have a requirement where i need to refresh cube daily automatically. > But > > i don't see any property or options in kylin 1.5.4.1. > > > > for ex: my hive fact and dimensions keep on loading daily basis, so that > > changes should reflect in kylin cube automatically. Please provide me > > solution to resolve. > > > > I dont find any option in kylin refresh tabe, i have only auto merge > > threshols,retension thresholds,partition start date options only. > > >
how to refresh cube automatically in kylin 1.5.4.1
Hi, I have a requirement where i need to refresh cube daily automatically. But i don't see any property or options in kylin 1.5.4.1. for ex: my hive fact and dimensions keep on loading daily basis, so that changes should reflect in kylin cube automatically. Please provide me solution to resolve. I dont find any option in kylin refresh tabe, i have only auto merge threshols,retension thresholds,partition start date options only.
