Github user kkhatua commented on the pull request:
https://github.com/apache/drill/pull/71#issuecomment-143909578
Closing pull request
---
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 fea
Github user kkhatua closed the pull request at:
https://github.com/apache/drill/pull/71
---
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 enabl
Github user dsbos commented on the pull request:
https://github.com/apache/drill/pull/71#issuecomment-143908786
@kkhatua, Can you close this pull request?
---
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 do
Github user dsbos commented on the pull request:
https://github.com/apache/drill/pull/71#issuecomment-143905747
This has been merged (commits 1dcf6cfb0d52435bcc7d1f4eada48fc0ce366dc4 and
a3ec52a721860a966dfa351f719458a200b27cbf).
---
If your project is set up for it, you can reply to
The github apache account is a read-only mirror of http://git.apache.org/ /
https://git-wip-us.apache.org/repos/asf?p=drill.git
(see http://www.apache.org/dev/git.html). So unfortunately, we don't get to
use the nice github pull mechanics.
Instead, you need to submit a patch for review on the Apac
GitHub user kkhatua opened a pull request:
https://github.com/apache/drill/pull/71
DRILL-2961: Throw SQLException when attempting to set query timeout
Statement.setQueryTimeout(int seconds) is a No-Op, leading the user to
believe that a timeout has been set. This provides the cor
