GitHub user techaddict opened a pull request:
https://github.com/apache/spark/pull/391
SPARK-1426: Make MLlib work with NumPy versions older than 1.7
Currently it requires NumPy 1.7 due to using the copyto method
(http://docs.scipy.org/doc/numpy/reference/generated
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40270135
Jenkins, retest this please.
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40270236
@mengxr yup, tests passed with 1.6
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/388#issuecomment-40271260
@pwendell can you review 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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40046556
@mateiz is there any other problem ?
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/370#issuecomment-40046601
@tgravescs any changes ?
---
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
Github user techaddict closed the pull request at:
https://github.com/apache/spark/pull/370
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/370#issuecomment-40059016
@pwendell after this commit i saw there are too many whitespaces in the
codebase, i've managed to fix them all, should i build a pull request for them ?
---
If your
GitHub user techaddict opened a pull request:
https://github.com/apache/spark/pull/380
Remove Unnecessary Whitespace's
stack these together in a commit else they show up chunk by chunk in
different commits.
You can merge this pull request into a Git repository by running
Github user techaddict closed the pull request at:
https://github.com/apache/spark/pull/356
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40120674
:smile:
---
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
GitHub user techaddict reopened a pull request:
https://github.com/apache/spark/pull/356
SPARK-1428: MLlib should convert non-float64 NumPy arrays to float64
instead of complaining
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user techaddict opened a pull request:
https://github.com/apache/spark/pull/388
SPARK-1469: Scheduler mode should accept lower-case definitions and have...
... nicer error messages
There are two improvements to Scheduler Mode:
1. Made the built in ones case
GitHub user techaddict opened a pull request:
https://github.com/apache/spark/pull/370
SPARK-1446: Spark examples should not do a System.exit
Spark examples should exit nice using SparkContext.stop() method, rather
than System.exit
System.exit can cause issues like in SPARK
GitHub user techaddict opened a pull request:
https://github.com/apache/spark/pull/356
SPARK-1428: MLlib should convert non-float64 NumPy arrays to float64
instead of complaining
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-39857157
@mengxr ok i'll try adding some test's
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/355#issuecomment-39857208
@pwendell yupp it is fully compatible although i'm checking every single
line :+1:
---
If your project is set up for it, you can reply to this email and have your
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-39927556
@mateiz updated, should i add tests too (IMHO i don't think there is need,
because its a trivial patch :smile: ) ?
---
If your project is set up for it, you can
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-39930653
You mean
`v = v.astype(float64, copy=True)`
---
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 techaddict opened a pull request:
https://github.com/apache/spark/pull/355
SPARK-1433: Upgrade Mesos dependency to 0.17.0
Mesos 0.13.0 was released 6 months ago.
Upgrade Mesos dependency to 0.17.0
You can merge this pull request into a Git repository by running
301 - 320 of 320 matches
Mail list logo
