Skip to content

Conversation

@prabeesh
Copy link
Contributor

modified to adhere to accepted coding standards as pointed by @tdas in PR #3844

@SparkQA
Copy link

SparkQA commented Jan 23, 2015

Test build #26020 has started for PR 4178 at commit 5857989.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Jan 23, 2015

Test build #26020 has finished for PR 4178 at commit 5857989.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26020/
Test FAILed.

@prabeesh
Copy link
Contributor Author

Jenkins, retest this please.

@SparkQA
Copy link

SparkQA commented Jan 23, 2015

Test build #26022 has started for PR 4178 at commit 5857989.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Jan 23, 2015

Test build #26022 has finished for PR 4178 at commit 5857989.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26022/
Test PASSed.

the hard coded '\tmp' may create garbage.
@SparkQA
Copy link

SparkQA commented Jan 23, 2015

Test build #26030 has started for PR 4178 at commit 66919a3.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Jan 23, 2015

Test build #26030 has finished for PR 4178 at commit 66919a3.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26030/
Test PASSed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see the point in swallowing this exception. Why not let it percolate, it will anyway print the stacktrace and stop the thread?

@SparkQA
Copy link

SparkQA commented Feb 3, 2015

Test build #26659 has started for PR 4178 at commit cd57029.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 3, 2015

Test build #26659 has finished for PR 4178 at commit cd57029.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26659/
Test PASSed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know how strong the convention is here, but I would have left the individual imports in this case.

@srowen
Copy link
Member

srowen commented Feb 7, 2015

Generally I'm liking the cleanup here, with a few questions inline. I think this deserves a JIRA too.

@prabeesh prabeesh changed the title [Minor][streaming][MQTT streaming] some trivial fixes [SPARK-5666][streaming][MQTT streaming] some trivial fixes Feb 7, 2015
@srowen
Copy link
Member

srowen commented Feb 9, 2015

This is just waiting on response to my comments. most of it is that some of the import movements put imports in the wrong place now. (Some are correct changes though.) I'm also concerned about the infinite loop if the queue is full.

@SparkQA
Copy link

SparkQA commented Feb 9, 2015

Test build #27113 has started for PR 4178 at commit 0cc67bd.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 9, 2015

Test build #27115 has started for PR 4178 at commit b042ad2.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 10, 2015

Test build #27216 has started for PR 4178 at commit 35f2cc3.

  • This patch merges cleanly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually which is the right import style. The below or existing ?

import org.eclipse.paho.client.mqttv3.{IMqttDeliveryToken, MqttCallback, MqttClient, MqttClientPersistence, MqttException, MqttMessage, MqttTopic}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the multiple import syntax is often used, especially where it's definitely shorter, but, I would not change it just to change it.

@SparkQA
Copy link

SparkQA commented Feb 10, 2015

Test build #27217 has started for PR 4178 at commit ccc0765.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 10, 2015

Test build #27215 has finished for PR 4178 at commit 46f9619.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27215/
Test PASSed.

@SparkQA
Copy link

SparkQA commented Feb 10, 2015

Test build #27216 has finished for PR 4178 at commit 35f2cc3.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27216/
Test PASSed.

@SparkQA
Copy link

SparkQA commented Feb 10, 2015

Test build #27217 has finished for PR 4178 at commit ccc0765.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27217/
Test PASSed.

@prabeesh
Copy link
Contributor Author

@srowen is there any more updates here?

@srowen
Copy link
Member

srowen commented Feb 16, 2015

@prabeesh this looks like it's waiting on a change to address the comment from @dragos - no need to catch and log the exception - and to the issue of infinite looping if the queue is full. I think it needs at least a warning that this is occurring. Yes it's an example that a 'real' deployment would have to change anyway, but I think it's worth showing good practice. Right now the error is always swallowed.

@SparkQA
Copy link

SparkQA commented Feb 24, 2015

Test build #27897 has started for PR 4178 at commit bba0d67.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 24, 2015

Test build #27897 has finished for PR 4178 at commit bba0d67.

  • This patch fails Scala style tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27897/
Test FAILed.

@SparkQA
Copy link

SparkQA commented Feb 24, 2015

Test build #27899 has started for PR 4178 at commit bd2cb49.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Feb 24, 2015

Test build #27899 has finished for PR 4178 at commit bd2cb49.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27899/
Test PASSed.

@prabeesh
Copy link
Contributor Author

@srowen warning that what is occurring.

@srowen
Copy link
Member

srowen commented Feb 25, 2015

@prabeesh eh OK you mean you addressed that comment? I still am not sure that the comment from @dragos was addressed as I mentioned before. But since that catch block was already there, may not matter much. The cleanup is minor and in a part of code unlikely to be hit by merge conflicts. I think the benefit is really slightly better resource management in this example, and handling a full queue. I'll merge soon if nobody objects.

@prabeesh
Copy link
Contributor Author

@srowen I think so I addressed the @dragos comments. Should we need more updates for that comments ?, If so could you please explain in detail ?

@dragos
Copy link
Contributor

dragos commented Feb 25, 2015

If my comment is the only thing that was holding this PR from merging, I withdraw my comment. :)

@prabeesh
Copy link
Contributor Author

@dragos no need of withdraw the comment.
Ultimately my aim to deliver good code to Spark users.

@asfgit asfgit closed this in d51ed26 Feb 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants