[jira] [Commented] (DRILL-8413) Add DNS Lookup Functions
[ https://issues.apache.org/jira/browse/DRILL-8413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701782#comment-17701782 ] ASF GitHub Bot commented on DRILL-8413: --- cgivre opened a new pull request, #2778: URL: https://github.com/apache/drill/pull/2778 # [DRILL-8413](https://issues.apache.org/jira/browse/DRILL-8413): Add DNS Lookup Functions ## Description See below ## Documentation These functions enable DNS research using Drill. * `getHostName()`: Returns the host name associated with an IP address. * `getHostAddress()`: Returns an IP address associated with a host name. * `dnsLookup(, [])`: Performs a DNS lookup on a given host. You can optionally provide a resolver. Possible resolver values are: `cloudflare`, `cloudflare_secondary`, `google`, `google_secondary`, `verisign`, `verisign_secondary`, `yandex`, `yandex_secondary`. * `whois(, [])`: Performs a whois lookup on the given host name. You can optionally provide a resolver URL. Note that not all providers allow bulk automated whois lookups, so please follow the terms fo service for your provider. ## Testing Added unit tests. > Add DNS Lookup Functions > > > Key: DRILL-8413 > URL: https://issues.apache.org/jira/browse/DRILL-8413 > Project: Apache Drill > Issue Type: New Feature > Components: Functions - Drill >Affects Versions: 1.21.0 >Reporter: Charles Givre >Assignee: Charles Givre >Priority: Major > Fix For: 1.22 > > > This PR adds additional DNS lookup functions to Drill: > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DRILL-8413) Add DNS Lookup Functions
Charles Givre created DRILL-8413: Summary: Add DNS Lookup Functions Key: DRILL-8413 URL: https://issues.apache.org/jira/browse/DRILL-8413 Project: Apache Drill Issue Type: New Feature Components: Functions - Drill Affects Versions: 1.21.0 Reporter: Charles Givre Assignee: Charles Givre Fix For: 1.22 This PR adds additional DNS lookup functions to Drill: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DRILL-8409) Support the configuration of bind addresses for network services
[
https://issues.apache.org/jira/browse/DRILL-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701684#comment-17701684
]
ASF GitHub Bot commented on DRILL-8409:
---
jnturton commented on PR #2777:
URL: https://github.com/apache/drill/pull/2777#issuecomment-1473742795
I've added two unrelated minor changes implementing safe calls to close()
methods. Currently when these calls fail due to some earlier error they drown
interesting messages out in unhelpful NPE noise.
> Support the configuration of bind addresses for network services
>
>
> Key: DRILL-8409
> URL: https://issues.apache.org/jira/browse/DRILL-8409
> Project: Apache Drill
> Issue Type: Bug
> Components: Server
>Affects Versions: 1.21.0
>Reporter: James Turton
>Assignee: James Turton
>Priority: Major
> Fix For: 1.21.1
>
>
> Drill provides the DRILL_HOST_NAME env var which determines what Drillbit
> host name will be exchanged over RPC for later look up by a remote client or
> Drillbit. This host name is used to check whether Drill is being asked to
> bind to the loopback address in distributed mode
> {code:java}
> if (isDistributedMode &&
> InetAddress.getByName(hostName).isLoopbackAddress()) {
> throw new DrillbitStartupException("Drillbit is disallowed to bind to
> loopback address in distributed mode.");
> }{code}
> but is not subsequently used set the bind address used for the Drillbit's RPC
> and web ports! This issue proposes that the Drillbit network services bind
> address is determined by DRILL_HOST_NAME.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DRILL-8412) Upgrade to Calcite 1.35-SNAPSHOT
[ https://issues.apache.org/jira/browse/DRILL-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8412: Description: This issue proposes that we try basing Drill master on snapshot builds of the upcoming version of Calcite so that the CI tests that run automatically upon commits to master will exercise Drill with present day Calcite. Breaking changes in Calcite would (mostly) break the Drill CI and force us to deal with them in order to proceed. Regressions in Calcite would (mostly) break the Drill CI and force us to report them in order to proceed. was: This issue proposes that we try basing Drill master on snapshot builds of the upcoming version of Calcite so that the CI tests that run automatically upon commits to master will exercise Drill with present day Calcite. Breaking changes in Calcite would (mostly) break the Drill CI and force us to deal with them in order to proceed. Regressions in Calcite would (mostly) break the Drill CI and force to report them in order to proceed. > Upgrade to Calcite 1.35-SNAPSHOT > > > Key: DRILL-8412 > URL: https://issues.apache.org/jira/browse/DRILL-8412 > Project: Apache Drill > Issue Type: Task > Components: SQL Parser >Reporter: James Turton >Assignee: James Turton >Priority: Major > > This issue proposes that we try basing Drill master on snapshot builds of the > upcoming version of Calcite so that the CI tests that run automatically upon > commits to master will exercise Drill with present day Calcite. > Breaking changes in Calcite would (mostly) break the Drill CI and force us to > deal with them in order to proceed. > Regressions in Calcite would (mostly) break the Drill CI and force us to > report them in order to proceed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-8412) Upgrade to Calcite 1.35-SNAPSHOT
[ https://issues.apache.org/jira/browse/DRILL-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-8412: Description: This issue proposes that we try basing Drill master on snapshot builds of the upcoming version of Calcite so that the CI tests that run automatically upon commits to master will exercise Drill with present day Calcite. 1. The CI tests that run automatically upon commits to Drill master will exercise Drill with present day Calcite. 2. Breaking changes in Calcite would (mostly) break the Drill CI and force us to deal with them in order to proceed. 3. Regressions in Calcite would (mostly) break the Drill CI and force to report them in order to proceed. 4. If Drill master becomes too unstable when it is based on Calcite snapshots then this change is trivially undoable. was: This issue proposes that we try basing Drill master on snapshot builds of the upcoming version of Calcite so that the CI tests that run automatically upon commits to master will exercise Drill with present day Calcite. Breaking changes in Calcite would (mostly) break the Drill CI and force us to deal with them in order to proceed. Regressions in Calcite would (mostly) break the Drill CI and force us to report them in order to proceed. > Upgrade to Calcite 1.35-SNAPSHOT > > > Key: DRILL-8412 > URL: https://issues.apache.org/jira/browse/DRILL-8412 > Project: Apache Drill > Issue Type: Task > Components: SQL Parser >Reporter: James Turton >Assignee: James Turton >Priority: Major > > This issue proposes that we try basing Drill master on snapshot builds of the > upcoming version of Calcite so that the CI tests that run automatically upon > commits to master will exercise Drill with present day Calcite. > 1. The CI tests that run automatically upon commits to Drill master will > exercise Drill with present day Calcite. > 2. Breaking changes in Calcite would (mostly) break the Drill CI and force us > to deal with them in order to proceed. > 3. Regressions in Calcite would (mostly) break the Drill CI and force to > report them in order to proceed. > 4. If Drill master becomes too unstable when it is based on Calcite snapshots > then this change is trivially undoable. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
