-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-5666][streaming][MQTT streaming] some trivial fixes #4178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Test build #26020 has started for PR 4178 at commit
|
|
Test build #26020 has finished for PR 4178 at commit
|
|
Test FAILed. |
|
Jenkins, retest this please. |
|
Test build #26022 has started for PR 4178 at commit
|
|
Test build #26022 has finished for PR 4178 at commit
|
|
Test PASSed. |
the hard coded '\tmp' may create garbage.
|
Test build #26030 has started for PR 4178 at commit
|
|
Test build #26030 has finished for PR 4178 at commit
|
|
Test PASSed. |
There was a problem hiding this comment.
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?
|
Test build #26659 has started for PR 4178 at commit
|
|
Test build #26659 has finished for PR 4178 at commit
|
|
Test PASSed. |
There was a problem hiding this comment.
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.
|
Generally I'm liking the cleanup here, with a few questions inline. I think this deserves a JIRA too. |
|
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. |
|
Test build #27113 has started for PR 4178 at commit
|
|
Test build #27115 has started for PR 4178 at commit
|
|
Test build #27216 has started for PR 4178 at commit
|
There was a problem hiding this comment.
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}There was a problem hiding this comment.
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.
|
Test build #27217 has started for PR 4178 at commit
|
|
Test build #27215 has finished for PR 4178 at commit
|
|
Test PASSed. |
|
Test build #27216 has finished for PR 4178 at commit
|
|
Test PASSed. |
|
Test build #27217 has finished for PR 4178 at commit
|
|
Test PASSed. |
|
@srowen is there any more updates here? |
|
@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. |
|
Test build #27897 has started for PR 4178 at commit
|
|
Test build #27897 has finished for PR 4178 at commit
|
|
Test FAILed. |
|
Test build #27899 has started for PR 4178 at commit
|
|
Test build #27899 has finished for PR 4178 at commit
|
|
Test PASSed. |
|
@srowen warning that what is occurring. |
|
@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 |
|
If my comment is the only thing that was holding this PR from merging, I withdraw my comment. :) |
|
@dragos no need of withdraw the comment. |
modified to adhere to accepted coding standards as pointed by @tdas in PR #3844