[QUESTION] Rest catalog TableScan API response's data_file has no 'metadataLocation'

[Ma, Limin]

Hi All,

/v1/{prefix}/namespaces/{namespace}/tables/{table}/plan
Response:
{

"file-scan-tasks": [

    {

      "data-file": {

        "file-path": "string",

        ...

       }

    }]

}



The spec does not indicate “data_file” has 'metadataLocation' property. But 
with Iceberg Vanilla local TableScan, DataFile (extends ContentFile) objects 
have ‘metadataLocation’ populated, which is used by MergingSnapshotProducer’s 
filterManager to efficiently identify relevant manifest files for filtering.

Any reason why Rest spec does not support that or will it be considered for 
support in future versions?

Thanks,
Limin