https://issues.apache.org/jira/browse/TEZ-4074

Which doesn't necessarily mean it's a bug,  but rather there are two
different versions of guava in the classpath. Can you continue the
conversation there?

On Sun, Mar 14, 2021, 10:45 AM Suryansh Agnihotri <
[email protected]> wrote:

> Hi Jonathan
> should I create a Jira for this?
>
> On Thu, 11 Mar 2021 at 15:47, Suryansh Agnihotri <
> [email protected]> wrote:
>
>> Hey Jonathan
>> I tried with 0.10.0 but now I am getting below error in the test.
>> Building doc does not mention any setup to be done. I just installed all
>> requirements mentioned in the doc.
>> I am using "mvn test -Dhadoop.version=3.1.2 -Phadoop3
>> -Dsurefire.rerunFailingTestsCount=3" to run the tests.
>>
>> [INFO] Running org.apache.tez.common.TestTezCommonUtils
>> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
>> 4.331 s <<< FAILURE! - in org.apache.tez.common.TestTezCommonUtils
>> [ERROR] org.apache.tez.common.TestTezCommonUtils  Time elapsed: 4.33 s
>>  <<< ERROR!
>> java.lang.NoSuchMethodError:
>> com.google.common.util.concurrent.Futures.addCallback(Lcom/google/common/util/concurrent/ListenableFuture;Lcom/google/common/util/concurrent/FutureCallback;)V
>> at
>> org.apache.tez.common.TestTezCommonUtils.setup(TestTezCommonUtils.java:65)
>>
>> On Wed, 10 Mar 2021 at 22:48, Suryansh Agnihotri <
>> [email protected]> wrote:
>>
>>> Thanks, I'll check the 0.10 branch and let you know if face any issues.
>>>
>>> On Wed, 10 Mar 2021 at 21:20, Jonathan Eagles <[email protected]> wrote:
>>>
>>>> Essentially, 0.10 and 0.9 are the same with the exception of hadoop 3.x
>>>> compatibility and a few minor changes. Both release lines are considered
>>>> active and fully supported. I will suggest development using the
>>>> branch-0.10.0 or master branch for this case. In this way if there are
>>>> other incompatibilities found, you can get the best support from the tez
>>>> open source community.
>>>>
>>>> Let me know if this helps guide you to a decision.
>>>>
>>>> On Wed, Mar 10, 2021 at 9:43 AM Suryansh Agnihotri <
>>>> [email protected]> wrote:
>>>>
>>>>> Hello Jonathan
>>>>> Thanks for the quick response. I am trying to build tez 0.9.2 with
>>>>> Hadoop 3.1.2.using "mvn package -Dhadoop.version=3.1.0 -Phadoop3".
>>>>> Will I be not able to use "branch-0.9.2", could you please specify if
>>>>> there are many compatibility issues observed/fixed wrt Hadoop 3.1+.
>>>>> If there are a few, can I just backport them in my "branch-0.92", will
>>>>> that make sense?
>>>>>
>>>>>
>>>>> On Wed, 10 Mar 2021 at 21:04, Jonathan Eagles <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Suryansh, thanks for reaching out to this email list. We are going to
>>>>>> need some more information about the issue. This message can occur for a
>>>>>> number of reasons. TEZ-3884 is most directly related to running tez 
>>>>>> against
>>>>>> hadoop 3.1+. Tez has created a new branch branch-0.10 to address hadoop 3
>>>>>> compatibility. If your issue is related to hadoop 3 compatibility, please
>>>>>> try tez 0.10.0 or branch-10.0 or even master branch. If you are running
>>>>>> against hadoop 2.x, then likely this is a different issue and will need
>>>>>> more understanding of client classpath setup as per
>>>>>> http://tez.apache.org/install.html.
>>>>>>
>>>>>> Regards,
>>>>>> jeagles
>>>>>>
>>>>>> On Wed, Mar 10, 2021 at 9:23 AM Suryansh Agnihotri <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hello
>>>>>>> I am facing the same issue
>>>>>>> https://issues.apache.org/jira/browse/TEZ-3884
>>>>>>> but this is marked as resolved.
>>>>>>> Could anyone please help with this.
>>>>>>>
>>>>>>> Tez branch: *branch-0.9.2*
>>>>>>>
>>>>>>> StackTrace:
>>>>>>> [ERROR] COMPILATION ERROR :
>>>>>>> [INFO] -------------------------------------------------------------
>>>>>>> [ERROR]
>>>>>>>
>>>>>>> /Users/suryansh/Documents/OSS/tez/tez-api/src/test/java/org/apache/tez/client/TestTezClientUtils.java:[48,30]
>>>>>>> cannot find symbol
>>>>>>>   symbol:   class DistributedFileSystem
>>>>>>>   location: package org.apache.hadoop.hdfs
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>

Reply via email to