Thanks Jianliang,
I saw jira assigned to you. Are you planning to provide a fix as well for
this?
If not, would you mind assigning to me?
-Vinay
On Wed, 28 Oct 2020 at 3:46 PM, Wu,Jianliang(vip.com) <
jianliang...@vipshop.com> wrote:
> Hi VinayaKumar and Wei-Chiu
>
> I filed jira https://iss
Hi Wu,Jianliang,
Have you created the Jira for the issue you mentioned due to
getContentSummary?
I might have a fix for this. Of-course it needs to be applied both client
and server side.
Let me know.
-Vinay
On Wed, Oct 14, 2020 at 12:26 PM Wu,Jianliang(vip.com) <
jianliang...@vipshop.com> wro
Thanks for the replies all!
> But in the opposite case, it might have problem, because 2.x server may
not understand new client calls added in 3.x
Yes not expecting this to work. I'm thinking about the case where one
upgrades existing 2.x clients to 3.x and expects it to still work against
2.x se
Ok, I will file a HDFS jira to report this issue.
> 2020年10月13日 20:43，Wei-Chiu Chuang 写道：
>
> Thanks Jialiang for reporting the issue.
> That sounds bad and should've not happened. Could you file a HDFS jira and
> fill in more details?
>
> On Mon, Oct 12, 2020 at 8:59 PM Wu,Jianliang(vip.com) <
>
In our case, when nn has upgraded to 3.1.3 and dn’s version was still 2.6, we
found hive to call getContentSummary method , the client and server was not
compatible because of hadoop3 added new PROVIDED storage type.
2020年10月13日 06:41，Chao Sun mailto:sunc...@apache.org>> 写道：
本电子邮件可能为保密文件。如果
Another backcompat issue was HDFS-15191, in 3.2.1.
But aside from that, we've been using 3x client libraries against both 2x and
3x clusters without issue.
On 10/13/20, 2:43 PM, "Wei-Chiu Chuang" wrote:
CAUTION: This email originates from an external party (outside of
Palantir). If you b
Thanks Jialiang for reporting the issue.
That sounds bad and should've not happened. Could you file a HDFS jira and
fill in more details?
On Mon, Oct 12, 2020 at 8:59 PM Wu,Jianliang(vip.com) <
jianliang...@vipshop.com> wrote:
> In our case, when nn has upgraded to 3.1.3 and dn’s version was stil
Hi,
I'm not a Hadoop expert but I've had some experiences in the cloud
infrastructure that I think also makes sense in your case.
For 2.x client + 3.x Server case, the Server side can obviously provide
compatibility, so it should work fine. But in the opposite case,
it might have problem, because
Hi community,
Does Hadoop 3.x provide wire compatibility between 3.x clients and 2.x
server? There is a blog post from Cloudera [1] mentioning wire
compatibility between 2.x clients and 3.x server, but not the other
direction. Curious if someone knows this. Also it'd be good to know if
someone is
