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 8B3B7200C4D for ; Wed, 5 Apr 2017 08:44:57 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 89C5E160B94; Wed, 5 Apr 2017 06:44:57 +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 C86DA160B91 for ; Wed, 5 Apr 2017 08:44:56 +0200 (CEST) Received: (qmail 43185 invoked by uid 500); 5 Apr 2017 06:44:56 -0000 Mailing-List: contact issues-help@eagle.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@eagle.apache.org Delivered-To: mailing list issues@eagle.apache.org Received: (qmail 43176 invoked by uid 99); 5 Apr 2017 06:44:55 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Apr 2017 06:44:55 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B8000DFCB3; Wed, 5 Apr 2017 06:44:55 +0000 (UTC) From: jhsenjaliya To: issues@eagle.apache.org Reply-To: issues@eagle.apache.org References: In-Reply-To: Subject: [GitHub] eagle issue #902: [EAGLE-985] Upgrade hbase dependency to 1.2.5 Content-Type: text/plain Message-Id: <20170405064455.B8000DFCB3@git1-us-west.apache.org> Date: Wed, 5 Apr 2017 06:44:55 +0000 (UTC) archived-at: Wed, 05 Apr 2017 06:44:57 -0000 Github user jhsenjaliya commented on the issue: https://github.com/apache/eagle/pull/902 Hi @qingwen220 no, since there are some function signature changes here, I dont think it will be compatible. ( without those changes, it is compatible though) so the question really comes down to whether we want to support 0.98 till 0.5 release then this can be pushed to 0.6 when majority of the tech stack is going to change ( storm, kafka, etc..), comment? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---