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 8B0E4200D06 for ; Mon, 11 Sep 2017 01:48:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 89BDC1609BD; Sun, 10 Sep 2017 23:48:05 +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 CFB801609C0 for ; Mon, 11 Sep 2017 01:48:04 +0200 (CEST) Received: (qmail 77837 invoked by uid 500); 10 Sep 2017 23:48:04 -0000 Mailing-List: contact dev-help@reef.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@reef.apache.org Delivered-To: mailing list dev@reef.apache.org Received: (qmail 77826 invoked by uid 99); 10 Sep 2017 23:48:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Sep 2017 23:48:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 66589183024 for ; Sun, 10 Sep 2017 23:48:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id GmBShl0bKUFo for ; Sun, 10 Sep 2017 23:48:01 +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 2D47E5FDBF for ; Sun, 10 Sep 2017 23:48:01 +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 5C085E00A7 for ; Sun, 10 Sep 2017 23:48:00 +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 118EE24143 for ; Sun, 10 Sep 2017 23:48:00 +0000 (UTC) Date: Sun, 10 Sep 2017 23:48:00 +0000 (UTC) From: "Markus Weimer (JIRA)" To: dev@reef.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (REEF-1882) Verify that REEF works with Protocol Buffers 3.x MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 10 Sep 2017 23:48:05 -0000 Markus Weimer created REEF-1882: ----------------------------------- Summary: Verify that REEF works with Protocol Buffers 3.x Key: REEF-1882 URL: https://issues.apache.org/jira/browse/REEF-1882 Project: REEF Issue Type: Task Reporter: Markus Weimer We currently rely on Google Protocol Buffers 2.5.x in both REEF Java and REEF.NET. However, that version doesn't officially support .NET. Newer versions, starting with 3.0, add official .NET support. We believe to be stuck with that version of it because that is the version Apache Hadoop YARN uses. It would be good to validate that assumption. Because if REEF Java does work on a YARN cluster using Protocol Buffers version 3.x, we could move to an officially supported version on the .NET side as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)