[
https://issues.apache.org/jira/browse/DRILL-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976673#comment-14976673
]
Jacques Nadeau commented on DRILL-3423:
---------------------------------------
The idea of the outputPath is where to position that value in the output record.
For example, the first three default I used were:
{code}
case "IP:connection.client.ip":
add(parser, path, writer.rootAsMap().map("client").varChar("ip"));
break;
case "IP:connection.client.peerip":
add(parser, path,
writer.rootAsMap().map("client").varChar("peer_ip"));
break;
case "IP:connection.server.ip":
add(parser, path, writer.rootAsMap().map("server").varChar("ip"));
{code}
those would become:
{code}
mapping: [
{httpdPath: "NUMBER:connection.client.logname", outputPath: "client.ip"}
{httpdPath: "IP:connection.client.peerip", outputPath: "client.peer_ip"}
{httpdPath: "IP:connection.server.ip", outputPath: "server.ip"}
]
{code}
In this example, "client.ip" would mean put this value in a field called ip
inside a map called client.
> Add New HTTPD format plugin
> ---------------------------
>
> Key: DRILL-3423
> URL: https://issues.apache.org/jira/browse/DRILL-3423
> Project: Apache Drill
> Issue Type: New Feature
> Components: Storage - Other
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
> Fix For: 1.3.0
>
>
> Add an HTTPD logparser based format plugin. The author has been kind enough
> to move the logparser project to be released under the Apache License. Can
> find it here:
> <dependency>
> <groupId>nl.basjes.parse.httpdlog</groupId>
> <artifactId>httpdlog-parser</artifactId>
> <version>2.0</version>
> </dependency>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
