hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7878) API - expose an unique file identifier
Date Thu, 26 Oct 2017 17:55:00 GMT

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

Sean Mackrory commented on HDFS-7878:
-------------------------------------

{quote}Wire compatibility with HDFS{quote}
How do commented out lines ensure wire compatibility? It would make sense if these were obsolete
fields and we didn't want to reuse obsolete number in case older messages get misinterpreted,
but then we should be reusing. Nevertheless, it appears we're not doing that in the latest
patch anymore.

I do think this resolves my previous concerns with the patch. In testCrossSerializationProto
and testJavaSerialization we're removing assertions that the PathHandle to what should be
the same file should be identical. Isn't that still true, and should be?

> API - expose an unique file identifier
> --------------------------------------
>
>                 Key: HDFS-7878
>                 URL: https://issues.apache.org/jira/browse/HDFS-7878
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>              Labels: BB2015-05-TBR
>         Attachments: HDFS-7878.01.patch, HDFS-7878.02.patch, HDFS-7878.03.patch, HDFS-7878.04.patch,
HDFS-7878.05.patch, HDFS-7878.06.patch, HDFS-7878.07.patch, HDFS-7878.08.patch, HDFS-7878.09.patch,
HDFS-7878.10.patch, HDFS-7878.11.patch, HDFS-7878.12.patch, HDFS-7878.13.patch, HDFS-7878.14.patch,
HDFS-7878.15.patch, HDFS-7878.16.patch, HDFS-7878.17.patch, HDFS-7878.18.patch, HDFS-7878.patch
>
>
> See HDFS-487.
> Even though that is resolved as duplicate, the ID is actually not exposed by the JIRA
it supposedly duplicates.
> INode ID for the file should be easy to expose; alternatively ID could be derived from
block IDs, to account for appends...
> This is useful e.g. for cache key by file, to make sure cache stays correct when file
is overwritten.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message