Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 2 May 2017 03:20:04 +0000 (UTC)
From: "Ted Dunning (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13063580.1492021512000.98797.1493695204980@Atlassian.JIRA>
In-Reply-To: <JIRA.13063580.1492021512000@Atlassian.JIRA>
References: <JIRA.13063580.1492021512000@Atlassian.JIRA> <JIRA.13063580.1492021512634@jira-lw-us.apache.org>
Subject: [jira] [Commented] (DRILL-5432) Want a memory format for PCAP files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 02 May 2017 03:20:10 -0000


    [ https://issues.apache.org/jira/browse/DRILL-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992131#comment-15992131 ] 

Ted Dunning commented on DRILL-5432:
------------------------------------

Grouping by TCP stream now works.

The only remaining significant issues are:

1) rebase to track master (should be trivial since all changes were to new files)

2) decide whether to support pcap-ng now or later (likely it will be later when somebody asks for it)

3) measure speed


> Want a memory format for PCAP files
> -----------------------------------
>
>                 Key: DRILL-5432
>                 URL: https://issues.apache.org/jira/browse/DRILL-5432
>             Project: Apache Drill
>          Issue Type: New Feature
>            Reporter: Ted Dunning
>
> PCAP files [1] are the de facto standard for storing network capture data. In security and protocol applications, it is very common to want to extract particular packets from a capture for further analysis.
> At a first level, it is desirable to query and filter by source and destination IP and port or by protocol. Beyond that, however, it would be very useful to be able to group packets by TCP session and eventually to look at packet contents. For now, however, the most critical requirement is that we should be able to scan captures at very high speed.
> I previously wrote a (kind of working) proof of concept for a PCAP decoder that did lazy deserialization and could traverse hundreds of MB of PCAP data per second per core. This compares to roughly 2-3 MB/s for widely available Apache-compatible open source PCAP decoders.
> This JIRA covers the integration and extension of that proof of concept as a Drill file format.
> Initial work is available at https://github.com/mapr-demos/drill-pcap-format
> [1] https://en.wikipedia.org/wiki/Pcap


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)