From issues-return-15693-archive-asf-public=cust-asf.ponee.io@kylin.apache.org Thu Jan 25 11:51:06 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id E33C8180676 for ; Thu, 25 Jan 2018 11:51:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id CE765160C13; Thu, 25 Jan 2018 10:51:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 296E9160C3D for ; Thu, 25 Jan 2018 11:51:06 +0100 (CET) Received: (qmail 45987 invoked by uid 500); 25 Jan 2018 10:51:05 -0000 Mailing-List: contact issues-help@kylin.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kylin.apache.org Delivered-To: mailing list issues@kylin.apache.org Received: (qmail 45978 invoked by uid 99); 25 Jan 2018 10:51:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2018 10:51:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EF02CC40C7 for ; Thu, 25 Jan 2018 10:51:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -108.711 X-Spam-Level: X-Spam-Status: No, score=-108.711 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id hIxqJq6QaxpP for ; Thu, 25 Jan 2018 10:51:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2281D5FC0E for ; Thu, 25 Jan 2018 10:51:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D87D9E0E80 for ; Thu, 25 Jan 2018 10:51:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C9B092411E for ; Thu, 25 Jan 2018 10:51:00 +0000 (UTC) Date: Thu, 25 Jan 2018 10:51:00 +0000 (UTC) From: "Billy Liu (JIRA)" To: issues@kylin.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KYLIN-1892) Support volatile range for segments auto merge MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KYLIN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-1892: ----------------------------- Summary: Support volatile range for segments auto merge (was: Support setting a volatile range for auto merge) > Support volatile range for segments auto merge > ---------------------------------------------- > > Key: KYLIN-1892 > URL: https://issues.apache.org/jira/browse/KYLIN-1892 > Project: Kylin > Issue Type: Improvement > Components: Job Engine > Affects Versions: v1.5.2 > Reporter: fengYu > Assignee: Yang Hao > Priority: Major > Fix For: v2.3.0 > > Attachments: KYLIN-1892.v3.patch > > > We always has some data need to be amended some days later > in current kylin, once I set Auto Merge Thresholds, the segment newly build will merge if reach Thresholds, the next day refresh will refresh merged segemnt, which is unnecessary. > So I want to add a interval configuration means auto merge will merge segments outside of the interval. > for example, if interval = 2, Auto Merge Thresholds=7, if 07-01 to 07-07 is built, auto merge will not trigger, when 07-09 built success, auto merge will trigger and merge segments from 07-01 to 07-07. -- This message was sent by Atlassian JIRA (v7.6.3#76005)