[GitHub] spark issue #15947: [SPARK-18447][DOCS] Fix the markdown for `Note:`/`NOTE:`...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15947
  
LGTM


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15729: [SPARK-18133] [branch-2.0] [Examples] [ML] [Pytho...

[jagadeesanas2]

Github user jagadeesanas2 closed the pull request at:

https://github.com/apache/spark/pull/15729


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15729: [SPARK-18133] [branch-2.0] [Examples] [ML] [Pytho...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15729

[SPARK-18133] [branch-2.0] [Examples] [ML] [Python ML Pipeline Exampl…

## What changes were proposed in this pull request?

[Fix] [branch-2.0] In Python 3, there is only one integer type (i.e., int), 
which mostly behaves like the long type in Python 2. Since Python 3 won't 
accept "L", so removed "L" in all examples.

## How was this patch tested?

Unit tests.

…e has syntax errors]

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-18133_branch2.0

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15729.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15729


commit dadfaa95bb72f867b0c7e06909e68cea53be5a93
Author: Jagadeesan 
Date:   2016-11-02T05:47:49Z

[SPARK-18133] [branch-2.0] [Examples] [ML] [Python ML Pipeline Example has 
syntax errors]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15728: [SPARK-18133] [branch-2.0] [Examples] [ML] [Pytho...

[jagadeesanas2]

Github user jagadeesanas2 closed the pull request at:

https://github.com/apache/spark/pull/15728


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #15660: [SPARK-18133][Examples] [ML] [Python ML Pipeline Example...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15660
  
@yanboliang PR for branch-2.0 https://github.com/apache/spark/pull/15728


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15728: [SPARK-18133] [branch-2.0] [Examples] [ML] [Pytho...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15728

[SPARK-18133] [branch-2.0] [Examples] [ML] [Python ML Pipeline Example has 
syntax errors]

## What changes were proposed in this pull request?

[Fix] [branch-2.0] In Python 3, there is only one integer type (i.e., int), 
which mostly behaves like the long type in Python 2. Since Python 3 won't 
accept "L", so removed "L" in all examples.

## How was this patch tested?

Unit tests.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-18133_2.0

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15728.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15728


commit 191d99692dc4315c371b566e3a9c5b114876ee49
Author: Wenchen Fan 
Date:   2016-09-01T00:54:59Z

[SPARK-17180][SPARK-17309][SPARK-17323][SQL][2.0] create AlterViewAsCommand 
to handle ALTER VIEW AS

## What changes were proposed in this pull request?

Currently we use `CreateViewCommand` to implement ALTER VIEW AS, which has 
3 bugs:

1. SPARK-17180: ALTER VIEW AS should alter temp view if view name has no 
database part and temp view exists
2. SPARK-17309: ALTER VIEW AS should issue exception if view does not exist.
3. SPARK-17323: ALTER VIEW AS should keep the previous table properties, 
comment, create_time, etc.

The root cause is, ALTER VIEW AS is quite different from CREATE VIEW, we 
need different code path to handle them. However, in `CreateViewCommand`, there 
is no way to distinguish ALTER VIEW AS and CREATE VIEW, we have to introduce 
extra flag. But instead of doing this, I think a more natural way is to 
separate the ALTER VIEW AS logic into a new command.

backport https://github.com/apache/spark/pull/14874 to 2.0

## How was this patch tested?

new tests in SQLViewSuite

Author: Wenchen Fan 

Closes #14893 from cloud-fan/minor4.

commit 8711b451d727074173748418a47cec210f84f2f7
Author: Junyang Qian 
Date:   2016-09-01T04:28:53Z

[SPARKR][MINOR] Fix windowPartitionBy example

## What changes were proposed in this pull request?

The usage in the original example is incorrect. This PR fixes it.

## How was this patch tested?

Manual test.

Author: Junyang Qian 

Closes #14903 from junyangq/SPARKR-FixWindowPartitionByDoc.

(cherry picked from commit d008638fbedc857c1adc1dff399d427b8bae848e)
Signed-off-by: Shivaram Venkataraman 

commit 6281b74b6965ffcd0600844cea168cbe71ca8248
Author: Shixiong Zhu 
Date:   2016-09-01T06:25:20Z

[SPARK-17318][TESTS] Fix ReplSuite replicating blocks of object with class 
defined in repl again

## What changes were proposed in this pull request?

After digging into the logs, I noticed the failure is because in this test, 
it starts a local cluster with 2 executors. However, when SparkContext is 
created, executors may be still not up. When one of the executor is not up 
during running the job, the blocks won't be replicated.

This PR just adds a wait loop before running the job to fix the flaky test.

## How was this patch tested?

Jenkins

Author: Shixiong Zhu 

Closes #14905 from zsxwing/SPARK-17318-2.

(cherry picked from commit 21c0a4fe9d8e21819ba96e7dc2b1f2999d3299ae)
Signed-off-by: Shixiong Zhu 

commit 13bacd7308c42c92f42fbc3ffbee9a13282668a9
Author: Tejas Patil 
Date:   2016-09-01T16:49:43Z

[SPARK-17271][SQL] Planner adds un-necessary Sort even if child orde…

## What changes were proposed in this pull request?

Ports https://github.com/apache/spark/pull/14841 and 
https://github.com/apache/spark/pull/14910 from `master` to `branch-2.0`

Jira : https://issues.apache.org/jira/browse/SPARK-17271

Planner is adding un-needed SORT operation due to bug in the way comparison 
for `SortOrder` is done at 
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/exchange/EnsureRequirements.scala#L253
`SortOrder` needs to be compared semantically because `Expression` within 
two `SortOrder` can be "semantically equal" but not literally equal objects.

eg. In case of `sql("SELECT * FROM table1 a JOIN table2 b ON 
a.col1=b.col1")`

Expression in required SortOrder:
```
  AttributeReference(
name = "col1",
dataType = LongType,
nullable = false
  ) (exprId = exprId,
qualifier = Some("a")
  )
```

Expression in child SortOrder:
```
  AttributeReference(
name =

[GitHub] spark pull request #15660: [SPARK-18133][Examples] [ML] [Python ML Pipeline ...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15660

[SPARK-18133][Examples] [ML] [Python ML Pipeline Example has syntax e…

## What changes were proposed in this pull request?

In Python 3, there is only one integer type (i.e., int), which mostly 
behaves like the long type in Python 2. Since Python 3 won't accept "L", so 
removed "L" in all examples.

## How was this patch tested?

Unit tests.

…rrors]

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-18133

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15660.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15660


commit 76d24a6559df150de28e991e316edf10e5e66022
Author: Jagadeesan 
Date:   2016-10-27T09:12:52Z

[SPARK-18133][Examples] [ML] [Python ML Pipeline Example has syntax errors]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15514: [SPARK-17960][PySpark] [Upgrade to Py4J 0.10.4]

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15514

[SPARK-17960][PySpark] [Upgrade to Py4J 0.10.4]

## What changes were proposed in this pull request?

1) Upgrade the Py4J version on the Java side
2) Update the py4j src zip file we bundle with Spark

## How was this patch tested?

Existing doctests & unit tests pass

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-17960

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15514.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15514


commit 70fa4555a75ad48676a3037c79a1bdb9230c3598
Author: Jagadeesan 
Date:   2016-10-17T14:21:04Z

[SPARK-17960][PySpark] [Upgrade to Py4J 0.10.4]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #15330: [SPARK-17718] [DOCS] [MLLIB] Make loss function formulat...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15330
  
@srowen now cleared... :+1: 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15293: [SPARK-17718] [Update MLib Classification Documen...

[jagadeesanas2]

Github user jagadeesanas2 closed the pull request at:

https://github.com/apache/spark/pull/15293


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #15293: [SPARK-17718] [Update MLib Classification Documentation]

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15293
  
Thanks @srowen :+1:  please go ahead 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #15309: [SPARK-17736] [Documentation][SparkR] [Update R README f...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15309
  
above means, your suggesting like this..?
``sudo pip install sphinx pypandoc``


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15293: [SPARK-17718] [Update MLib Classification Documen...

[jagadeesanas2]

Github user jagadeesanas2 commented on a diff in the pull request:

https://github.com/apache/spark/pull/15293#discussion_r81468699
  
--- Diff: docs/mllib-linear-methods.md ---
@@ -78,6 +78,10 @@ methods `spark.mllib` supports:
   
 
 
+A binary label y is denoted as either +1 (positive) or −1 (negative), 
which is
--- End diff --

Removed duplicates


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15309: [SPARK-17736] [Documentation][SparkR] [Update R R...

[jagadeesanas2]

Github user jagadeesanas2 commented on a diff in the pull request:

https://github.com/apache/spark/pull/15309#discussion_r81467019
  
--- Diff: docs/README.md ---
@@ -21,6 +21,8 @@ installed. Also install the following libraries:
 # Following is needed only for generating API docs
 $ sudo pip install sphinx
 $ sudo Rscript -e 'install.packages(c("knitr", "devtools", "roxygen2", 
"testthat"), repos="http://cran.stat.ucla.edu/";)'
+$ sudo Rscript -e 'install.packages(c("rmarkdown"), 
repos="http://cran.stat.ucla.edu/";)'
+$ sudo pip install pandoc pandoc-citeproc
--- End diff --

+1 on just keeping ``sudo pip install pypandoc``


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15293: [SPARK-17718] [Update MLib Classification Documen...

[jagadeesanas2]

Github user jagadeesanas2 commented on a diff in the pull request:

https://github.com/apache/spark/pull/15293#discussion_r81466956
  
--- Diff: docs/mllib-linear-methods.md ---
@@ -78,6 +78,10 @@ methods `spark.mllib` supports:
   
 
 
+A binary label y is denoted as either +1 (positive) or −1 (negative), 
which is
--- End diff --

Can i keep it only below statement...?

``Note: The negative label is represented by 0 in spark.mllib instead of 
−1, to be consistent with multiclass labeling.``


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15293: [SPARK-17718] [Update MLib Classification Documen...

[jagadeesanas2]

Github user jagadeesanas2 commented on a diff in the pull request:

https://github.com/apache/spark/pull/15293#discussion_r81462301
  
--- Diff: docs/mllib-linear-methods.md ---
@@ -78,6 +78,10 @@ methods `spark.mllib` supports:
   
 
 
+A binary label y is denoted as either +1 (positive) or −1 (negative), 
which is
--- End diff --

As mentioned in the JIRA, i simply added detailed documentation to avoid 
future confusion.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15309: [SPARK-17736] [Documentation][SparkR] [Update R R...

[jagadeesanas2]

Github user jagadeesanas2 commented on a diff in the pull request:

https://github.com/apache/spark/pull/15309#discussion_r81462265
  
--- Diff: docs/README.md ---
@@ -21,6 +21,8 @@ installed. Also install the following libraries:
 # Following is needed only for generating API docs
 $ sudo pip install sphinx
 $ sudo Rscript -e 'install.packages(c("knitr", "devtools", "roxygen2", 
"testthat"), repos="http://cran.stat.ucla.edu/";)'
+$ sudo Rscript -e 'install.packages(c("rmarkdown"), 
repos="http://cran.stat.ucla.edu/";)'
+$ sudo pip install pandoc pandoc-citeproc
--- End diff --

@felixcheung i agree, if we are installing manually on Ubuntu/Debain we 
need to install using below command
``sudo apt-get install pandoc pandoc-citeproc``

similarly for
Fedora/Red Hat: ``sudo yum install pandoc``
Arch: ``sudo pacman -S pandoc``
Mac OS X with Homebrew: ``brew install pandoc pandoc-citeproc 
Caskroom/cask/mactex``
Machine with Haskell: ``cabal-install pandoc``

@srowen  
TTBOMK, as it's python package, it can be manage via pip also
https://pypi.python.org/pypi/pypandoc


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #15309: [SPARK-17736] [Documentation][SparkR] [Update R README f...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15309
  
@srowen  yes


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15309: [SPARK-17736] [Documentation][SparkR] [Update R R...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15309

[SPARK-17736] [Documentation][SparkR] [Update R README for rmarkdown,…

## What changes were proposed in this pull request?

To build R docs (which are built when R tests are run), users need to 
install pandoc and rmarkdown. This was done for Jenkins in 
~~[SPARK-17420](https://issues.apache.org/jira/browse/SPARK-17420)~~

… pandoc]

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-17736

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15309.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15309


commit ac6a8c49dcc53450765b9e192bb685144c681e99
Author: Jagadeesan 
Date:   2016-09-30T05:23:22Z

[SPARK-17736] [Documentation][SparkR] [Update R README for rmarkdown, 
pandoc]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #15293: [SPARK-17718] [Update MLib Classification Documentation]

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15293
  

![app1](https://cloud.githubusercontent.com/assets/20658072/18951136/09c46ac0-8661-11e6-974e-a04939de08b7.png)
The hinge loss provides a relatively tight, convex upper bound on the 0–1 
indicator function. Specifically, the hinge loss equals the 0–1 indicator 
function. 
Source: 
https://en.wikipedia.org/wiki/Loss_functions_for_classification#Hinge_loss

@srowen  any suggestion..?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15293: [SPARK-17718] [Update MLib Classification Documen...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15293

[SPARK-17718] [Update MLib Classification Documentation]

## What changes were proposed in this pull request?

The loss function here for logistic regression is confusing. It seems to 
imply that spark uses only -1 and 1 class labels. However it uses 0,1. Added 
detailed documentation to avoid confusion.





You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-17718

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15293.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15293


commit 210dc851c64ce6192438ad9d2750878e493669ff
Author: Jagadeesan 
Date:   2016-09-29T07:55:49Z

[SPARK-17718] [Update MLib Classification Documentation]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #15108: [SPARK-17543] [Missing log4j config file for tests in co...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/15108
  
yes, its some what similar to ```common/network-shuffle```


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15108: [SPARK-17543] [Missing log4j config file for test...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15108

[SPARK-17543] [Missing log4j config file for tests in common/network-…

## What changes were proposed in this pull request?

The Maven module `common/network-shuffle` does not have a log4j 
configuration file for its test cases. So, added `log4j.properties` in the 
directory `src/test/resources`. 

…shuffle]

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-17543

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15108.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15108


commit f476755bf7653bca008d3e32375424c769ddb835
Author: Jagadeesan 
Date:   2016-09-15T05:56:01Z

[SPARK-17543] [Missing log4j config file for tests in 
common/network-shuffle]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15042: [SPARK-17449] [Documentation] [Relation between h...

[jagadeesanas2]

Github user jagadeesanas2 commented on a diff in the pull request:

https://github.com/apache/spark/pull/15042#discussion_r78533096
  
--- Diff: core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala ---
@@ -32,6 +32,8 @@ import org.apache.spark.util._
  * A heartbeat from executors to the driver. This is a shared message used 
by several internal
  * components to convey liveness or execution information for in-progress 
tasks. It will also
  * expire the hosts that have not heartbeated for more than 
spark.network.timeout.
+ * spark.executor.heartbeatInterval configuration value is certainly 
intended to be much
--- End diff --

Thanks for correcting me..!! I will edit and send PR once again.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #15042: [SPARK-17449] [Documentation] [Relation between h...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/15042

[SPARK-17449] [Documentation] [Relation between heartbeatInterval and…

## What changes were proposed in this pull request?

The relation between spark.network.timeout and 
spark.executor.heartbeatInterval should be mentioned in the document. 

… network timeout]

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-17449

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/15042.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15042


commit 83031c4d285db633c6468ef8471810765f62c0be
Author: Jagadeesan 
Date:   2016-09-10T05:49:41Z

[SPARK-17449] [Documentation] [Relation between heartbeatInterval and 
network timeout]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #14711: [SPARK-16822] [DOC] [Support latex in scaladoc wi...

[jagadeesanas2]

Github user jagadeesanas2 closed the pull request at:

https://github.com/apache/spark/pull/14711


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #14688: [SPARK-17095] [Documentation] [Latex and Scala doc do no...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/14688
  
@srowen I do not find any other instances. Perhaps I send some fixes for 
Latex string.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #14711: [SPARK-16822] [DOC] [Support latex in scaladoc with Math...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/14711
  
ohh i got it. Can i close this 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 does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #14711: [SPARK-16822] [DOC] [Support latex in scaladoc with Math...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/14711
  
@srowen , Actually this fix (mathjax issues) for this JIRA only. As @sethah 
mentioned in his comment, he is working on `SPARK-17095`, he will send PR soon. 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #14715: [SPARK-17085] [Streaming] [Documentation and actu...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/14715

[SPARK-17085] [Streaming] [Documentation and actual code differs - 
Unsupported Operations]



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-17085

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/14715.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14715


commit 6d1c52f24c7df2c3be7a2d0340d2caf8438f6708
Author: Jagadeesan 
Date:   2016-08-19T08:26:30Z

[SPARK-17085] [Streaming] [Documentation and actual code differs - 
Unsupported Operations]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark issue #14711: [SPARK-16822] [DOC] [Support latex in scaladoc with Math...

[jagadeesanas2]

Github user jagadeesanas2 commented on the issue:

https://github.com/apache/spark/pull/14711
  
cc @lins05 @srowen 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #14711: [SPARK-16822] [DOC] [Support latex in scaladoc wi...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/14711

[SPARK-16822] [DOC] [Support latex in scaladoc with MathJax]

## What changes were proposed in this pull request?

LaTeX is rendered as simple code, in `LinearRegression.scala`
```scala
{{{
 L = 1/2n||\sum_i w_i(x_i - \bar{x_i}) / \hat{x_i} - (y - \bar{y}) / 
\hat{y}||^2 + regTerms
}}}
```


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-16822

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/14711.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14711


commit 7cacb111390b2ca9531053444c631f914b864bc4
Author: Jagadeesan 
Date:   2016-08-19T05:45:32Z

[SPARK-16822] [DOC] [Support latex in scaladoc with MathJax]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #14688: [SPARK-17095] [Documentation] [Latex and Scala do...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/14688

[SPARK-17095] [Documentation] [Latex and Scala doc do not play nicely]

## What changes were proposed in this pull request?

In Latex, it is common to find "}}}" when closing several expressions at 
once. [SPARK-16822](https://issues.apache.org/jira/browse/SPARK-16822) added 
Mathjax to render Latex equations in scaladoc. However, when scala doc sees 
"}}}" or "{{{" it treats it as a special character for code block. This results 
in some very strange output.










You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-17095

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/14688.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14688


commit d50990cebea21fdd298559ff002b9c5fd0e2e294
Author: Jagadeesan 
Date:   2016-08-17T12:20:43Z

[SPARK-17095] [Documentation] [Latex and Scala doc do not play nicely]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #14596: [SPARK-12370] [Documentation] [Documentation shou...

[jagadeesanas2]

GitHub user jagadeesanas2 opened a pull request:

https://github.com/apache/spark/pull/14596

[SPARK-12370] [Documentation] [Documentation should link to examples …

## What changes were proposed in this pull request?

When documentation is built is should reference examples from the same 
build. There are times when the docs have links that point to files in the 
GitHub head which may not be valid on the current release. Changed that in URLs 
to make them point to the right tag in git using ```SPARK_VERSION_SHORT```

…from its own release version] [Streaming programming guide]

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ibmsoe/spark SPARK-12370

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/14596.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14596


commit f2f867af70c0981b796b1df60a7614d2435440de
Author: Jagadeesan 
Date:   2016-08-11T06:40:32Z

[SPARK-12370] [Documentation] [Documentation should link to examples from 
its own release version] [Streaming programming guide]




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org