Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/1
@gatorsmile we fix it in SPARK 1.6.2, and take in use for two month. For
further reason, I give one pr on master branch. I will test it next week
GitHub user morenn520 opened a pull request:
https://github.com/apache/spark/pull/1
JDBC support date/timestamp type as partitionColumn
Jira: https://issues.apache.org/jira/browse/SPARK-22814
PartitionColumn must be a numeric column from the table.
However
Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/17872
@jerryshao done.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
Github user morenn520 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17872#discussion_r115191861
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -48,9 +50,16 @@ private
Github user morenn520 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17872#discussion_r115188391
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -48,9 +50,16 @@ private
Github user morenn520 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17872#discussion_r115184514
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -48,9 +50,16 @@ private
Github user morenn520 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17872#discussion_r115183402
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/security/HadoopFSCredentialProvider.scala
---
@@ -48,9 +50,16 @@ private
Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/17872
@srowen @jerryshao @steveloughran This is the latest PR. #17870 is
deprecated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user morenn520 closed the pull request at:
https://github.com/apache/spark/pull/17870
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/17870
@srowen thanks. See PR in master branch:
https://github.com/apache/spark/pull/17872
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
GitHub user morenn520 opened a pull request:
https://github.com/apache/spark/pull/17872
[SPARK-20608] allow standby namenodes in spark.yarn.access.namenodes (PR in
master branch)
Related Jira:
https://issues.apache.org/jira/browse/SPARK-20608
Descriptions:
See PR
Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/17870
@jerryshao Why not submit PR for master branch?
Sorry, I didnt find yarn module in master branch..If this patch can be
accepted, I would spend some time to read codes in master branch. Up
GitHub user morenn520 opened a pull request:
https://github.com/apache/spark/pull/17870
[SPARK-20608] allow standby namenodes in spark.yarn.access.namenodes
## What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-20608
## How
Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/17238
Thanks @tgravescs , we has used a dynamic topology discovery script to
avoid this problem. Since tez and mr donât do this, maybe spark could not fix
this problem.
---
If your project is set
Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/17238
@squito Actually it's a misconfiguration in our yarn. There are thousands
of nodes in our production yarn. It will be quite frequent to rack/unrack
nodes, so as to make something missing easily
GitHub user morenn520 opened a pull request:
https://github.com/apache/spark/pull/17238
getRackForHost returns None if host is unknown by driver
## What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-19894
## How
16 matches
Mail list logo