Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9EBA3200C5A for ; Tue, 4 Apr 2017 06:32:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9D247160B9C; Tue, 4 Apr 2017 04:32:45 +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 E5899160B8F for ; Tue, 4 Apr 2017 06:32:44 +0200 (CEST) Received: (qmail 46169 invoked by uid 500); 4 Apr 2017 04:32:44 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 46156 invoked by uid 99); 4 Apr 2017 04:32:44 -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; Tue, 04 Apr 2017 04:32:43 +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 A445CC0291 for ; Tue, 4 Apr 2017 04:32:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 AnZjf1zLUb0T for ; Tue, 4 Apr 2017 04:32:43 +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 995F15F5C6 for ; Tue, 4 Apr 2017 04:32:42 +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 DA114E0012 for ; Tue, 4 Apr 2017 04:32:41 +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 97AD121D63 for ; Tue, 4 Apr 2017 04:32:41 +0000 (UTC) Date: Tue, 4 Apr 2017 04:32:41 +0000 (UTC) From: "Pramod Immaneni (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (APEXMALHAR-2473) Support for global cache meta information in db CacheManager MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 04 Apr 2017 04:32:45 -0000 Pramod Immaneni created APEXMALHAR-2473: ------------------------------------------- Summary: Support for global cache meta information in db CacheManager Key: APEXMALHAR-2473 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2473 Project: Apache Apex Malhar Issue Type: Improvement Reporter: Pramod Immaneni Currently db CacheManager has no knowledge of characteristics of the data or the cache stores, so it handles all cases uniformly. This may not be optimal implementation in all cases. Better optimizations can be performed in the manager if this information is known. A few examples, if the data is read-only the keys in the primary cache need not be refreshed like they are being done daily, if the primary cache size is known the number of initial entries loaded from backup needn't exceed it. Add support for supplying such general cache meta information in the manager. -- This message was sent by Atlassian JIRA (v6.3.15#6346)