fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-976459364
Oh, I haven't spotted that, fixed. Let's see the CI results. Thank you
@sodonnel for the review!
--
This is an automated message from the Apache Git Service.
To respond to the
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-975483356
At the end of the day after an extensive discussion, we agreed with @symious
[here](https://github.com/apache/hadoop/pull/3658#discussion_r752898939), to
continue with this solut
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-968314417
@symious
I have created #3658 if you have time please review, if it is ok, please add
your review there.
I am closing this PR for now, as we discussed to implement the
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-965758819
@symious ah I see what you are thinking about, and what I have assumed about
the proposal and its impact is not correct.
Actually after looking into this further, and revie
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-964018510
@symious
thank you for the discussion so far, as CI got green, may I ask if you are
ok with the solution based on the reasoning I provided?
--
This is an automated message
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-962377604
@symious I would say yes, and no :)
We have 3 levels in the communication, the DfsClient which connects to HDFS,
and is one of many users of the SASL protocol layer (SaslRp
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-961304051
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscri
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-961304051
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscri
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-961311596
@sodonnel I still owe this PR with some kind of test, the prior test failure
should be fixed now, but it has revealed that there were some behaviour change
caused by my prior cha
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-961304051
@symious Let me correct a bit about the case, but in general you see it the
right way.
We have a code that uses FS API to connect to the cluster. This code creates
client
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-958358986
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscri
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-958364897
@sodonnel thank you for the review (and sorry for the delay, I was off last
week), also I have an idea on how to add a test for this case to demonstrate
the problem better, I am
fapifta commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-958358986
@symious actually the connection is not two different connection, but the
same connection to the same DataNode. The problem is with what we send via the
connection. In a secure e
13 matches
Mail list logo
