[
https://issues.apache.org/jira/browse/DRILL-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549187#comment-16549187
]
ASF GitHub Bot commented on DRILL-6179:
---------------------------------------
Vlad-Storona commented on issue #1126: DRILL-6179: Added pcapng-format support
URL: https://github.com/apache/drill/pull/1126#issuecomment-406254685
@paul-rogers thanks for the review. I solved all the issues. Also, I rebased
to the latest master and solved conflicts. Can you take a look at changes?
Also, I found a problem with a DRILL-6104, because of it I have had
conflicts with a master branch. The problem was with proto files. In DRILL-6104
was edited generated files in `drill-protocol` module without regeneration. I
updated the proto file with an information about my plugin and DRILL-6104.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Added pcapng-format support
> ---------------------------
>
> Key: DRILL-6179
> URL: https://issues.apache.org/jira/browse/DRILL-6179
> Project: Apache Drill
> Issue Type: New Feature
> Affects Versions: 1.13.0
> Reporter: Vlad
> Assignee: Vlad
> Priority: Major
> Labels: doc-impacting
> Fix For: 1.14.0
>
>
> The _PCAP Next Generation Dump File Format_ (or pcapng for short) [1] is an
> attempt to overcome the limitations of the currently widely used (but
> limited) libpcap format.
> At a first level, it is desirable to query and filter by source and
> destination IP and port, and src/dest mac addreses 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.
> Initial work is available at
> https://github.com/mapr-demos/drill/tree/pcapng_dev
> [1] https://pcapng.github.io/pcapng/
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
