[
https://issues.apache.org/jira/browse/DRILL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995033#comment-15995033
]
ASF GitHub Bot commented on DRILL-3867:
---------------------------------------
GitHub user vdiravka opened a pull request:
https://github.com/apache/drill/pull/824
DRILL-3867: Store relative paths in metadata file
For easier review this PR consists of two commits, which can be squashed
into one.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vdiravka/drill DRILL-3867
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/824.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #824
----
commit c2341e21e00ec595cab66d078c37ffcaf8e2481e
Author: Steven Phillips <[email protected]>
Date: 2015-10-02T03:36:15Z
DRILL-3867: Store relative paths in metadata file
commit 6ff28a8c94e7f1a9a79d75132695f8335f315cdd
Author: Vitalii Diravka <[email protected]>
Date: 2017-05-03T15:52:08Z
DRILL-3867: Store relative paths in metadata file
- resolving conflicts;
- refactoring according to the new changes in the Metadata and other
classes,
that were made after this original fix.
----
> Store relative paths in metadata file
> -------------------------------------
>
> Key: DRILL-3867
> URL: https://issues.apache.org/jira/browse/DRILL-3867
> Project: Apache Drill
> Issue Type: Bug
> Components: Metadata
> Affects Versions: 1.2.0
> Reporter: Rahul Challapalli
> Assignee: Vitalii Diravka
> Fix For: Future
>
>
> git.commit.id.abbrev=cf4f745
> git.commit.time=29.09.2015 @ 23\:19\:52 UTC
> The below sequence of steps reproduces the issue
> 1. Create the cache file
> {code}
> 0: jdbc:drill:zk=10.10.103.60:5181> refresh table metadata
> dfs.`/drill/testdata/metadata_caching/lineitem`;
> +-------+-------------------------------------------------------------------------------------+
> | ok | summary
> |
> +-------+-------------------------------------------------------------------------------------+
> | true | Successfully updated metadata for table
> /drill/testdata/metadata_caching/lineitem. |
> +-------+-------------------------------------------------------------------------------------+
> 1 row selected (1.558 seconds)
> {code}
> 2. Move the directory
> {code}
> hadoop fs -mv /drill/testdata/metadata_caching/lineitem /drill/
> {code}
> 3. Now run a query on top of it
> {code}
> 0: jdbc:drill:zk=10.10.103.60:5181> select * from dfs.`/drill/lineitem` limit
> 1;
> Error: SYSTEM ERROR: FileNotFoundException: Requested file
> maprfs:///drill/testdata/metadata_caching/lineitem/2006/1 does not exist.
> [Error Id: b456d912-57a0-4690-a44b-140d4964903e on pssc-66.qa.lab:31010]
> (state=,code=0)
> {code}
> This is obvious given the fact that we are storing absolute file paths in the
> cache file
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
