Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1386#issuecomment-62491569
OK I have a couple things to do this and next week. HW Spain. But after
that lets get together and talk.
On Mon, Nov 10, 2014 at 8:30 PM, Tathagata Das
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1893#issuecomment-51936244
+1
I'm all for the update to 0.98 HBase.
Just make sure we address everything that Sean O is asking. We need this
to be able to build with Hadoop1
Github user tmalaska closed the pull request at:
https://github.com/apache/spark/pull/1608
---
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 tmalaska opened a pull request:
https://github.com/apache/spark/pull/1608
Spark-2447 : Spark on HBase
Add common solution for sending upsert actions to HBase (put, deletes,
and increment)
This is the first pull request: mainly to test the review process
GitHub user tmalaska opened a pull request:
https://github.com/apache/spark/pull/1386
SPARK-1642: Upgrade FlumeInputDStream's FlumeReceiver to support FLUME-2083
This will allow encryption with SSL between Flume and Spark
You can merge this pull request into a Git repository
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536448
Man I'm sorry this is taking so long. Thank you for your help.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1347#issuecomment-48536862
Yes let me figure that out now.
---
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 tmalaska closed the pull request at:
https://github.com/apache/spark/pull/566
---
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1168#issuecomment-48537088
Done. I closed 566.
Anything else. I'm open to work on anything. Just direct me to a jira.
---
If your project is set up for it, you can reply to this email
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1168#issuecomment-48400281
Let me know if I need to do anything
---
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1168#issuecomment-47044140
Let me know if there is anything I can do to help.
On Jun 24, 2014 6:33 PM, Tathagata Das notificati...@github.com wrote:
This is a weird binary
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-46755792
I'm going to have to make a new pull request, because I had drop the repo
that belonged to this pull request. I will update the ticket with the
information when it's
GitHub user tmalaska opened a pull request:
https://github.com/apache/spark/pull/1168
SPARK-1478.2: Upgrade FlumeInputDStream's FlumeReceiver to support
FLUME-1915
SPARK-1478.2: Upgrade FlumeInputDStream's FlumeReceiver to support
FLUME-1915
You can merge this pull request
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-46763419
New Pull request https://github.com/apache/spark/pull/1168
---
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/1168#issuecomment-46767307
Thanks tdas I messed that one. I just updated. It should be good now.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-46724152
Let me know if there is anything I can do to help this go through.
Thanks tdas
On Fri, Jun 20, 2014 at 4:38 PM, Tathagata Das notificati
Github user tmalaska commented on a diff in the pull request:
https://github.com/apache/spark/pull/566#discussion_r14040514
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/FlumeInputDStream.scala
---
@@ -134,22 +144,64 @@ private[streaming]
class
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-46726131
No worries. I'm starting to free up so I would love to do more work. I
will finish this one up then the Flume encryption one. Then if you have
anything else. Let me
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-46372202
Hey tdas,
I was going to do 1642 tonight, but I noticed these changes are not in the
code yet. What should I do?
Thanks
---
If your project is set up
GitHub user tmalaska opened a pull request:
https://github.com/apache/spark/pull/
Spark-2173 : Add Master Computer and SuperStep ...
Add Master Computer and SuperStep Accumulator to Pregel GraphX
Implemention
You can merge this pull request into a Git repository by running
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/#issuecomment-46391395
Wait, this isn't going to get me what I want, because I can't read the
ssAccumulator in the vprog. I think I will have to change to a boardcast. I
will
---
If your
Github user tmalaska closed the pull request at:
https://github.com/apache/spark/pull/
---
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/#issuecomment-46391465
Never mind. I had to close the pull request. I thought about it. The
ccAccumulator is not accessible from the vprog which was my goal. I'm going to
have to use
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-42189283
LOL tdas, how it going. Just pinging.
---
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-41949374
Hey tdas,
How is this Jira looking. Is there anything I need to do to get it passed?
---
If your project is set up for it, you can reply to this email and have
Github user tmalaska closed the pull request at:
https://github.com/apache/spark/pull/405
---
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-41732028
I already updated the code and tested it. Feel free to commit unless you
see anything wrong.
If you commit it in the next couple hours. I can start on SPARK
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-41546071
OK I have reviewed the commits and I will be making changes this morning.
Thank tdas.
---
If your project is set up for it, you can reply to this email and have your
Github user tmalaska commented on a diff in the pull request:
https://github.com/apache/spark/pull/566#discussion_r12044638
--- Diff:
external/flume/src/test/scala/org/apache/spark/streaming/flume/FlumeStreamSuite.scala
---
@@ -85,4 +108,14 @@ class FlumeStreamSuite extends
Github user tmalaska commented on a diff in the pull request:
https://github.com/apache/spark/pull/566#discussion_r12044643
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/FlumeInputDStream.scala
---
@@ -153,3 +181,15 @@ class FlumeReceiver
Github user tmalaska commented on a diff in the pull request:
https://github.com/apache/spark/pull/566#discussion_r12044730
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/FlumeUtils.scala
---
@@ -66,6 +84,23 @@ object FlumeUtils {
port: Int
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/566#issuecomment-41631586
Will do. I will start tomorrow. Shouldn't take long.
---
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 tmalaska opened a pull request:
https://github.com/apache/spark/pull/566
SPARK-1478: Upgrade FlumeInputDStream's FlumeReceiver to support FLUME-1915
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tmalaska/spark
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41283871
OK this should be good now. Please review
---
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
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41309801
@pwendell this is a great question.
The answer there is ether a bug in sbt or I'm missing something in the
SparkBuild.scala.
In the Flume 1.4.0 pom.xml
Github user tmalaska commented on a diff in the pull request:
https://github.com/apache/spark/pull/507#discussion_r11960961
--- Diff: project/SparkBuild.scala ---
@@ -605,7 +606,8 @@ object SparkBuild extends Build {
name := spark-streaming-flume,
previousArtifact
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41316256
@pwendell I thought that too then I noticed the following two parts of the
Flume 1.4.0 file
//
profile
idhadoop-1.0/id
activation
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41316558
Soo the tags didn't make it through the last one. Here are the parts of
the pom.xml again.
{profile}
{id}hadoop-2{/id}
{activation
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41316766
@berngp I undated pull request name as you recommended.
---
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 tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41317846
Yes this is my first Spark commit. So I'm going to make some mistakes. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41319131
@pwendell to be honest this is a little deeper then I normally go with Pom
specification.
I think we are there is a behavior that maven does
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41323794
@srowen yes I agree. Yes I missed that one. The maven will do 7 and sbt
will do 8.
I will move the maven to 8 as well.
---
If your project is set up
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41331043
So what should we do? Flume 1.2.0 is even worse at Thrift 6.1.
There are some people still on Hadoop 1 but most are on Hadoop 2 now
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41335079
Good point @srowen we may be able to just exclude thrift all together. All
we need is the avro source stuff.
I will exclude from both and see if it works
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41344456
Uploaded the exclude all and I ran a assembly and test-quick and it worked.
Let me know what I should do next.
Thanks again for the help.
---
If your
GitHub user tmalaska opened a pull request:
https://github.com/apache/spark/pull/507
SPARK-1584
Updated the Flume dependency in the maven pom file and the scala build file.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tmalaska
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/507#issuecomment-41164979
There is a build issue. Related to thrift.version. THis pull request
should be consider involved.
Researching now.
---
If your project is set up for it, you
GitHub user tmalaska opened a pull request:
https://github.com/apache/spark/pull/405
SPARK-1478
Initial Version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tmalaska/spark master
Alternatively you can review and apply
Github user tmalaska commented on the pull request:
https://github.com/apache/spark/pull/405#issuecomment-40421425
Yeah no problem. Thanks for taking the time to review my code. This is my
first time committing with Scala :)
Just let me know when ( #300 ) is done and I
49 matches
Mail list logo
