I rather move to Hadoop 2.7.4, if the release day is near.
On Tue, Dec 6, 2016 at 7:33 PM, Roman Shaposhnik
wrote:
> Soo what's the consensus here?
>
> Thanks,
> Roman.
>
> On Wed, Nov 30, 2016 at 11:15 AM, Akira Ajisaka
> wrote:
> > Hi,
> >
Soo what's the consensus here?
Thanks,
Roman.
On Wed, Nov 30, 2016 at 11:15 AM, Akira Ajisaka
wrote:
> Hi,
>
> I've created a patch for Apache Giraph to compile with Hadoop 2.7.3.
> https://issues.apache.org/jira/browse/GIRAPH-1110
>
> Is it work for you?
>
>
Hi,
I've created a patch for Apache Giraph to compile with Hadoop 2.7.3.
https://issues.apache.org/jira/browse/GIRAPH-1110
Is it work for you?
Regards,
Akira
On 2016/11/29 7:38, Roman Shaposhnik wrote:
On Mon, Nov 28, 2016 at 11:10 AM, Olaf Flebbe wrote:
Hi,
I vote for
Sorry I was refering to GIRAPH-1110. A patch to Giraph not Hadoop.
Olaf
> Am 28.11.2016 um 23:38 schrieb Roman Shaposhnik :
>
> On Mon, Nov 28, 2016 at 11:10 AM, Olaf Flebbe wrote:
>> Hi,
>>
>> I vote for patching Giraph according to GIRAPH-1112, since
+1 on hadoop 3 development build..
On Mon, Nov 28, 2016 at 4:38 PM, Roman Shaposhnik
wrote:
> On Mon, Nov 28, 2016 at 11:10 AM, Olaf Flebbe wrote:
> > Hi,
> >
> > I vote for patching Giraph according to GIRAPH-1112, since it will be a
> future-proof (i.e.
On Mon, Nov 28, 2016 at 11:10 AM, Olaf Flebbe wrote:
> Hi,
>
> I vote for patching Giraph according to GIRAPH-1112, since it will be a
> future-proof (i.e. Hadoop-2.8.x) work around. Additionally, the list of
> issues resolved by hadoop-2.7.3 is rather long.
I'm confused.
Hi,
I vote for patching Giraph according to GIRAPH-1112, since it will be a
future-proof (i.e. Hadoop-2.8.x) work around. Additionally, the list of issues
resolved by hadoop-2.7.3 is rather long.
Olaf
> Am 28.11.2016 um 16:06 schrieb MrAsanjar . :
>
> As part of Bigtop
As part of Bigtop release 1.2 road-map, I upgraded hadoop to version 2.7.3
last week. Unfortunately it appears the recent changes (HADOOP-11252) in
Hadoop 2.7.3 has broken source-level compatibility resulting in Apache
Graph build-break. This issue has been reported by