HeartSaVioR edited a comment on pull request #31427:
URL: https://github.com/apache/spark/pull/31427#issuecomment-777141815
Please don't get me wrong. This PR doesn't take any approval from anyone
including contributors before merging. I'm also pretty sure most committees
folks wait
HeartSaVioR edited a comment on pull request #31427:
URL: https://github.com/apache/spark/pull/31427#issuecomment-777141815
Please don't get me wrong. This PR doesn't take any approval from anyone
including contributors before merging. I'm also pretty sure most committees
folks wait
HeartSaVioR edited a comment on pull request #31427:
URL: https://github.com/apache/spark/pull/31427#issuecomment-776580168
I tend to agree that limiting the namespace only on session catalog isn't
good and I really would like to see bright solution which addresses this, but
the new
HeartSaVioR edited a comment on pull request #31427:
URL: https://github.com/apache/spark/pull/31427#issuecomment-776580168
I tend to agree that limiting the namespace only on session catalog isn't
good and I really would like to see bright solution which addresses this, but
the new
HeartSaVioR edited a comment on pull request #31427:
URL: https://github.com/apache/spark/pull/31427#issuecomment-776580168
I tend to agree that limiting the namespace only on session catalog isn't
good and I really would like to see bright solution which addresses this, but
the new
HeartSaVioR edited a comment on pull request #31427:
URL: https://github.com/apache/spark/pull/31427#issuecomment-776562258
I'm not feeling good with this too, but not from the code diff, but from the
process.
I understand lazy consensus on code is applied by default ASF policy (if
