[
https://issues.apache.org/jira/browse/HDFS-14665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDFS-14665:
------------------------------
Description:
WebHDFS:
{code:java}
GET /webhdfs/v1/tmp/?op=LISTSTATUS&user.name=hdfs HTTP/1.1
{code}
{code}
{
"FileStatuses": {
"FileStatus": [
...
{
"accessTime": 0,
"blockSize": 0,
"childrenNum": 0,
"fileId": 16395,
"group": "hadoop",
"length": 0,
"modificationTime": 1563893395614,
"owner": "mapred",
"pathSuffix": "logs",
"permission": "1777",
"replication": 0,
"storagePolicy": 0,
"type": "DIRECTORY"
}
]
}
}
{code}
HttpFS:
{code:java}
GET /webhdfs/v1/tmp/?op=LISTSTATUS&user.name=hdfs HTTP/1.1
{code}
{code}
{
"FileStatuses": {
"FileStatus": [
...
{
"pathSuffix": "logs",
"type": "DIRECTORY",
"length": 0,
"owner": "mapred",
"group": "hadoop",
"permission": "1777",
"accessTime": 0,
"modificationTime": 1563893395614,
"blockSize": 0,
"replication": 0
}
]
}
}
{code}
You can see the same LISTSTATUS request to HttpFS is missing 3 fields:
{code}
"childrenNum" (directories only?)
"fileId"
"storagePolicy"
{code}
The same applies to LISTSTATUS_BATCH, which might be using the same underlying
calls to compose the response.
Also may file another Jira to align the order of the keys in the responses.
was:
WebHDFS:
{code:java}
GET /webhdfs/v1/tmp/?op=LISTSTATUS&user.name=hdfs HTTP/1.1
{code}
{code}
{
"FileStatuses": {
"FileStatus": [
...
{
"accessTime": 0,
"blockSize": 0,
"childrenNum": 0,
"fileId": 16395,
"group": "hadoop",
"length": 0,
"modificationTime": 1563893395614,
"owner": "mapred",
"pathSuffix": "logs",
"permission": "1777",
"replication": 0,
"storagePolicy": 0,
"type": "DIRECTORY"
}
]
}
}
{code}
HttpFS:
{code:java}
GET /webhdfs/v1/tmp/?op=LISTSTATUS&user.name=hdfs HTTP/1.1
{code}
{code}
{
"FileStatuses": {
"FileStatus": [
...
{
"pathSuffix": "logs",
"type": "DIRECTORY",
"length": 0,
"owner": "mapred",
"group": "hadoop",
"permission": "1777",
"accessTime": 0,
"modificationTime": 1563893395614,
"blockSize": 0,
"replication": 0
}
]
}
}
{code}
You can see the same LISTSTATUS request to HttpFS is missing 3 fields:
{code}
childrenNum (directories only?)
fileId
storagePolicy.
{code}
The same applies to LISTSTATUS_BATCH, which might be using the same underlying
calls to compose the response.
Also may file another Jira to align the order of the keys in the responses.
> HttpFS: LISTSTATUS result is missing some fields for each entry
> ---------------------------------------------------------------
>
> Key: HDFS-14665
> URL: https://issues.apache.org/jira/browse/HDFS-14665
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
>
> WebHDFS:
> {code:java}
> GET /webhdfs/v1/tmp/?op=LISTSTATUS&user.name=hdfs HTTP/1.1
> {code}
> {code}
> {
> "FileStatuses": {
> "FileStatus": [
> ...
> {
> "accessTime": 0,
> "blockSize": 0,
> "childrenNum": 0,
> "fileId": 16395,
> "group": "hadoop",
> "length": 0,
> "modificationTime": 1563893395614,
> "owner": "mapred",
> "pathSuffix": "logs",
> "permission": "1777",
> "replication": 0,
> "storagePolicy": 0,
> "type": "DIRECTORY"
> }
> ]
> }
> }
> {code}
> HttpFS:
> {code:java}
> GET /webhdfs/v1/tmp/?op=LISTSTATUS&user.name=hdfs HTTP/1.1
> {code}
> {code}
> {
> "FileStatuses": {
> "FileStatus": [
> ...
> {
> "pathSuffix": "logs",
> "type": "DIRECTORY",
> "length": 0,
> "owner": "mapred",
> "group": "hadoop",
> "permission": "1777",
> "accessTime": 0,
> "modificationTime": 1563893395614,
> "blockSize": 0,
> "replication": 0
> }
> ]
> }
> }
> {code}
> You can see the same LISTSTATUS request to HttpFS is missing 3 fields:
> {code}
> "childrenNum" (directories only?)
> "fileId"
> "storagePolicy"
> {code}
> The same applies to LISTSTATUS_BATCH, which might be using the same
> underlying calls to compose the response.
> Also may file another Jira to align the order of the keys in the responses.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
