[
https://issues.apache.org/jira/browse/MAPREDUCE-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takanobu Asanuma resolved MAPREDUCE-7350.
-
Fix Version/s: 3.4.0
Resolution: Fixed
> Replace Guava Lists usage
Viraj Jasani created MAPREDUCE-7350:
---
Summary: Replace Guava Lists usage by Hadoop's own Lists in
hadoop-mapreduce-project
Key: MAPREDUCE-7350
URL: https://issues.apache.org/jira/browse/MAPREDUCE
+1
Thanks for initiating this Weichiu.
-Dinesh
On Sat, Apr 4, 2020 at 3:13 PM Wei-Chiu Chuang wrote:
> Hi Hadoop devs,
>
> I spent a good part of the past 7 months working with a dozen of colleagues
> to update the guava version in Cloudera's software (that includes Hadoo
colleagues
to update the guava version in Cloudera's software (that includes Hadoop,
HBase, Spark, Hive, Cloudera Manager ... more than 20+ projects)
After 7 months, I finally came to a conclusion: Update to Hadoop 3.3 /
3.2.1 / 3.1.3, even if you just go from Hadoop 3.0/ 3.1.0 is going to be
really
a dozen of
> colleagues
> > to update the guava version in Cloudera's software (that includes Hadoop,
> > HBase, Spark, Hive, Cloudera Manager ... more than 20+ projects)
> >
> > After 7 months, I finally came to a conclusion: Update to Hadoop 3.3 /
> > 3.2.1 /
+1
-Ayush
> On 05-Apr-2020, at 12:43 AM, Wei-Chiu Chuang wrote:
>
> Hi Hadoop devs,
>
> I spent a good part of the past 7 months working with a dozen of colleagues
> to update the guava version in Cloudera's software (that includes Hadoop,
> HBase, Spark, Hive, Clou
+1
Masatake Iwasaki
On 2020/04/06 10:32, Akira Ajisaka wrote:
+1
Thanks,
Akira
On Sun, Apr 5, 2020 at 4:13 AM Wei-Chiu Chuang wrote:
Hi Hadoop devs,
I spent a good part of the past 7 months working with a dozen of colleagues
to update the guava version in Cloudera's software
+1
Thanks,
Akira
On Sun, Apr 5, 2020 at 4:13 AM Wei-Chiu Chuang wrote:
> Hi Hadoop devs,
>
> I spent a good part of the past 7 months working with a dozen of colleagues
> to update the guava version in Cloudera's software (that includes Hadoop,
> HBase, Spark, Hive, Cloud
Great question!
I can run Java API Compliance Checker to detect any API changes. Guess
that's the only one to find out.
On Sat, Apr 4, 2020 at 1:19 PM Igor Dvorzhak wrote:
> How this proposal will impact public APIs? I.e does Hadoop expose any
> Guava classes in the client API
How this proposal will impact public APIs? I.e does Hadoop expose any Guava
classes in the client APIs that will require recompiling all client
applications because they need to use shaded Guava classes?
On Sat, Apr 4, 2020 at 12:13 PM Wei-Chiu Chuang wrote:
> Hi Hadoop devs,
>
> I spe
Hi Hadoop devs,
I spent a good part of the past 7 months working with a dozen of colleagues
to update the guava version in Cloudera's software (that includes Hadoop,
HBase, Spark, Hive, Cloudera Manager ... more than 20+ projects)
After 7 months, I finally came to a conclusion: Update to H
; On Tue, Apr 2, 2019 at 9:54 AM Steve Loughran wrote:
>
> >
> > I know that the number of guava updates we could call painless is 0, but
> > we need to do this.
> >
> > The last time we successfully updated Guava was 2012: h
> > ttps://issues.apache.org/jira/br
I am taking silence as happiness here.
+1 to the patch
On Tue, Apr 2, 2019 at 9:54 AM Steve Loughran wrote:
>
> I know that the number of guava updates we could call painless is 0, but
> we need to do this.
>
> The last time we successfully updated Guava was 2012: h
> ttps:/
I know that the number of guava updates we could call painless is 0, but we
need to do this.
The last time we successfully updated Guava was 2012: h
ttps://issues.apache.org/jira/browse/HDFS-3187
That was the java 6 era
The last unsuccessful attempt, April 2017:
https://issues.apache.org/jira
I'm usually an advocate for getting rid of unnecessary dependencies
(cough, jetty, cough), but a lot of the things in Guava are really
useful.
Immutable collections, BiMap, Multisets, Arrays#asList, the stuff for
writing hashCode() and equals(), String#Joiner, the list goes on. We
particu
like the idea of isolating usage of guava that
breaks with guava 16 and later. I assume (but I haven't looked into it)
that it's fairly straightforward to isolate them and fix them. That work
could be done at any time without any version upgrades or impacting users.
On Mon, Nov 10,
ogether a prototype
of how #2 would work (I don't think it will be more than 200 lines of code)
On Mon, Nov 10, 2014 at 5:18 AM, Steve Loughran
wrote:
> Yes, Guava is a constant pain; there's lots of open JIRAs related to it, as
> its the one we can't seamlessly upgrade. Not
Yes, Guava is a constant pain; there's lots of open JIRAs related to it, as
its the one we can't seamlessly upgrade. Not unless we do our own fork and
reinsert the missing classes.
The most common uses in the code are
@VisibleForTesting (easily replicated)
and the Precondition.check()
… has been a constant pain w.r.t compatibility etc.
Should we consider adopting a policy to not use guava in Common/HDFS/YARN?
MR doesn't matter too much since it's application-side issue, it does hurt
end-users though since they still might want a newer guava-version, but at
leas
Christopher Tubbs created MAPREDUCE-6083:
Summary: Map/Reduce dangerously adds Guava @Beta class to
CryptoUtils
Key: MAPREDUCE-6083
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6083
Zhihong Ted Yu created MAPREDUCE-4429:
-
Summary: Upgrade Guava for critical performance bug fix
Key: MAPREDUCE-4429
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4429
Project: Hadoop Map
guava-r09 JAR file needs to be added to mapreduce.
--
Key: MAPREDUCE-2627
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2627
Project: Hadoop Map/Reduce
Issue Type: Bug
22 matches
Mail list logo
