kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Han (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KYLIN-952) User can trigger a Refresh job on an non-existing cube segment via REST API
Date Tue, 25 Aug 2015 02:59:49 GMT

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

Luke Han updated KYLIN-952:
---------------------------
    Sprint: Sprint 46, Sprint 47, Sprint 48  (was: Sprint 46, Sprint 47)

> User can trigger a Refresh job on an non-existing cube segment via REST API
> ---------------------------------------------------------------------------
>
>                 Key: KYLIN-952
>                 URL: https://issues.apache.org/jira/browse/KYLIN-952
>             Project: Kylin
>          Issue Type: Bug
>          Components: REST Service
>    Affects Versions: v0.7.2
>            Reporter: Shaofeng SHI
>            Assignee: Shaofeng SHI
>             Fix For: v0.8.1, v0.7.3
>
>
> This is a bug reported in eBay internal user, internal JIRA ID is KYLIN-285;
> The user triggered a Refresh job on a cube segment "July 12 - July 13"; The job moved
to the second last step and reported an error:
> {code}
> java.lang.IllegalStateException: For cube CUBE[name=pvp], segment CubeSegment{uuid=fb9d27a5-577f-40c8-9459-41997a57f243,
create_time_utc:=1439849872596, name=20150712000000_20150713000000, last_build_job_id=544e1e12-d222-4820-a4c1-5e28ae18fd65,
status=NEW} is expected but not in the tobe [CubeSegment{uuid=51be77b4-12e1-47e5-8218-be496b6a0723,
create_time_utc:=1439500003158, name=20150501000000_20150708000000, last_build_job_id=725f9023-346f-421e-9513-b40cca1162ec,
status=READY}, CubeSegment{uuid=f804e890-e291-4a9b-bbde-bdacc1bcf59c, create_time_utc:=1439595378977,
name=20150708000000_20150801000000, last_build_job_id=128e3ba6-49b2-4d29-8b0a-f65ce2440e54,
status=READY}, CubeSegment{uuid=b7d061f9-77ab-41d8-99ad-9dafacb3e813, create_time_utc:=1439592377757,
name=20150801000000_20150807000000, last_build_job_id=65f089cb-2a60-4e6a-b449-521b537da778,
status=READY}]
>     at org.apache.kylin.cube.CubeManager.promoteNewlyBuiltSegments(CubeManager.java:508)
>     at org.apache.kylin.job.cube.UpdateCubeInfoAfterBuildStep.doWork(UpdateCubeInfoAfterBuildStep.java:130)
>     at org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107)
>     at org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:51)
>     at org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107)
>     at org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:130)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>     at java.lang.Thread.run(Thread.java:745)
> {code}
> Actually the segment of "July 12 - July 13" doesn't exit, it had been merged into a bigger
segment;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message