Github user jyotiska closed the pull request at:
https://github.com/apache/spark/pull/68
---
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 is
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36825757
@mateiz @JoshRosen Can you verify this?
---
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
Github user jyotiska closed the pull request at:
https://github.com/apache/spark/pull/83
---
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 is
Github user jyotiska commented on a diff in the pull request:
https://github.com/apache/spark/pull/83#discussion_r10330490
--- Diff: docs/python-programming-guide.md ---
@@ -146,7 +146,7 @@ sc = SparkContext(conf = conf)
# API Docs
-[API documentation](api
GitHub user jyotiska opened a pull request:
https://github.com/apache/spark/pull/83
Fixed link for latest pyspark api guide
Fixed link for PySpark API in Python programming guide to the latest
version.
You can merge this pull request into a Git repository by running:
$ git
Github user jyotiska closed the pull request at:
https://github.com/apache/spark/pull/67
---
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 is
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/68#issuecomment-36586048
I was meaning to ask about this. Can we do something to display the docs
properly on both Github and website? I was bothered by how ugly the code
snippets look when
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/67#issuecomment-36585916
I understand. Actually, all these links in Python programming guide was
throwing 404. Not sure if this is only with me, but if the links are working
fine for you I will
GitHub user jyotiska opened a pull request:
https://github.com/apache/spark/pull/68
Updated the formatting of code blocks using Github flavored markdown
Github does not work with "highlight" to format code blocks which turns
them into plain text. In this PR, I used Githu
GitHub user jyotiska opened a pull request:
https://github.com/apache/spark/pull/67
Fixed API docs link in Python programming guide
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jyotiska/spark pyspark_docs3
Alternatively you
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36484436
I think namedtuple will be more suitable. @mateiz What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jyotiska closed the pull request at:
https://github.com/apache/spark/pull/23
---
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 is
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36414522
Can one of the admins look into this?
---
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
GitHub user jyotiska opened a pull request:
https://github.com/apache/spark/pull/34
[SPARK-972] Added detailed callsite info for ValueError in context.py
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jyotiska/spark
Github user jyotiska commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r10117264
--- Diff: python/setup.py ---
@@ -0,0 +1,30 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/26#issuecomment-36225645
+1 It will be better if these projects were made separate from core-spark
project and grown as independent projects. This keeps the core project lean and
helps to grow
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/23#issuecomment-36216611
Right, didn't notice that PR.
---
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 doe
GitHub user jyotiska opened a pull request:
https://github.com/apache/spark/pull/23
Updated more links in documentation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jyotiska/spark pyspark_docs2
Alternatively you can review
18 matches
Mail list logo
