Typically when you use the MapR-FS plugin you don’t need to specify the cluster
root path in the dfs workspace.
Instead of "location": "/mapr/cluster3", use "location": "/",
"connection": "maprfs:///", already points to the default MapR cluster root.
--Andries
On 9/11/17, 2:23 AM, "Takeo Ogawara" <ta-ogaw...@kddi-research.jp> wrote:
Dear all,
I’m using PCAP storage plugin over MapR FS(5.2.0) with Drill(1.11.0)
compiled as follows.
$ mvn clean install -DskipTests -Pmapr
Some queries caused errors as following.
Does anyone know how to solve these errors?
1. Query error when cluster-name is not specified
Storage “mfs” setting is this.
> "type": "file",
> "enabled": true,
> "connection": "maprfs:///",
> "config": null,
> "workspaces": {
> "root": {
> "location": "/mapr/cluster3",
> "writable": false,
> "defaultInputFormat": null
> }
> }
With this setting, the following query failed.
> select * from mfs.`x.pcap` ;
> Error: DATA_READ ERROR: /x.pcap (No such file or directory)
>
> File name: /x.pcap
> Fragment 0:0
>
> [Error Id: 70b73062-c3ed-4a10-9a88-034b4e6d039a on node21:31010]
(state=,code=0)
But these queries passed.
> select * from mfs.root.`x.pcap` ;
> select * from mfs.`x.csv`;
> select * from mfs.root.`x.csv`;
2. Large PCAP file
Query on very large PCAP file (larger than 100GB) failed with following
error message.
> Error: SYSTEM ERROR: IllegalStateException: Bad magic number = 0a0d0d0a
>
> Fragment 1:169
>
> [Error Id: 8882c359-c253-40c0-866c-417ef1ce5aa3 on node22:31010]
(state=,code=0)
This happens even on Linux FS not MapR FS
Thank you.
