drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tdunning <...@git.apache.org>
Subject [GitHub] drill issue #831: DRILL-5432: Added pcap-format support
Date Sat, 01 Jul 2017 02:18:28 GMT
Github user tdunning commented on the issue:

    On Fri, Jun 30, 2017 at 5:34 PM, Paul Rogers <notifications@github.com>
    > That only works if Drill has an autoloading capability that allows storage
    > formats to be loaded and authenticated easily.
    > Why? To get pcap in 1.11, one must install a new Drill version, which
    > requires a restart. Assuming that pcap were a separate project, you'd
    > install a new jar, and restart. Neither provides auto loading.
    No. But if I have 1.11 already and decide that I want pcap (or any similar
    data format), it would be nice if I could do the equivalent of pip (for
    python) or install.packages("...") (for R) or mvn test (for Java) and get
    whatever cool capability I like.
    This may be described as "just install a new jar" but the convenience level
    is a proven Big Deal (tm). It would even be possible to leverage Maven
    central to make it happen, but there needs to be convenience sugar around
    the process to make it consumable.
    > Not clear on the authentication issue. If a plugin were a separate
    > project, wouldn't that project have a way of certifying its jars?
    Dunno. Not some random project.
    If Drill requires it, then yes.  And I am saying that Drill should require
    resolution back to some level of trust.

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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message