maartenhubrechts-anb commented on PR #696:
URL: 
https://github.com/apache/arrow-rs-object-store/pull/696#issuecomment-4842074792

   **Still reproduces as of 2026-06-30** (independent of LakeSail — different 
tenant, North Europe region), so adding a data point to the "is it fixed on the 
OneLake side?" question.
   
   `deltalake` 1.6.0 (object_store Azure) reads still fail with `Generic delta 
kernel error: No files in log segment`. I captured the actual wire traffic via 
a TLS-intercepting proxy. The kernel's log listing is:
   
   ```
   GET /<workspace>?restype=container&comp=list
       &prefix=<lakehouse>/Tables/<schema>/<table>/_delta_log/
       
&startFrom=<lakehouse>/Tables/<schema>/<table>/_delta_log/00000000000000000000
   ```
   
   Replaying that exact `List Blobs` by hand, varying only `startFrom`, against 
an unmodified token:
   
   | `startFrom` | blobs returned |
   |---|---|
   | *(omitted)* | `…/_delta_log/00000000000000000000.json`, `…0001.json` |
   | `…/_delta_log/00000000000000000000` (what object_store sends) | **none** |
   | `…/_delta_log/` (the prefix itself) | **none** |
   
   Any non-empty `startFrom` yields an empty result — including values that 
sort *before* the target files (`…00000000000000000000` < 
`…00000000000000000000.json`), which a compliant response must still return. 
The empty response is **HTTP 200 with `<Blobs />` and an empty `<NextMarker 
/>`** — i.e. a final page, not a pagination continuation, so this is 
server-side and not object_store under-fetching.
   
   Reproduces identically on two different table types:
   - a Lakehouse schema-shortcut table (GUID-form abfss URL), and
   - a Warehouse table (friendly-name abfss URL).
   
   So whatever was deployed, `startFrom` on this region/tenant still returns 
empty for `_delta_log` listings. Happy to provide more captures if useful.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to