Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
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.
Attachments
Attachments
Issue Links
- blocks
-
HDFS-14159 Backporting HDFS-12882 to branch-3.0: Support full open(PathHandle) contract in HDFS
- Resolved
- breaks
-
HADOOP-15031 Fix javadoc issues in Hadoop Common
- Resolved
- contains
-
HDFS-10262 Change HdfsFileStatus::fileId to an opaque identifier
- Resolved
- is blocked by
-
HDFS-6984 Serialize FileStatus via protobuf
- Resolved
- is depended upon by
-
HDFS-11640 [READ] Datanodes should use a unique identifier when reading from external stores
- Resolved
- is related to
-
HDFS-12681 Make HdfsLocatedFileStatus a subtype of LocatedFileStatus
- Resolved
-
HDFS-12882 Support full open(PathHandle) contract in HDFS
- Resolved
-
HDFS-12877 Add open(PathHandle) with default buffersize
- Resolved
- relates to
-
HDFS-487 HDFS should expose a fileid to uniquely identify a file
- Resolved
-
HDFS-9806 Allow HDFS block replicas to be provided by an external storage system
- Resolved