You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "makssent (via GitHub)" <gi...@apache.org> on 2026/07/08 07:22:06 UTC
[I] Support op_seek_blob operation in Firebird Proxy [shardingsphere]
makssent opened a new issue, #39051:
URL: https://github.com/apache/shardingsphere/issues/39051
# Feature Request
**Is your feature request related to a problem?**
Firebird Proxy does not support the op_seek_blob operation.
**Describe the feature you would like.**
Implement op_seek_blob in Firebird Proxy: reposition the read offset of an opened BLOB according to the requested seek mode and offset, and return the resulting position in the response (as fbclient and Jaybird expect). Seek is only valid for stream BLOBs, matching Firebird server behavior.
--
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: notifications-unsubscribe@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Support op_seek_blob operation in Firebird Proxy [shardingsphere]
Posted by "rishi-rana (via GitHub)" <gi...@apache.org>.
rishi-rana commented on issue #39051:
URL: https://github.com/apache/shardingsphere/issues/39051#issuecomment-5861872044
I would like to work on this, with a deadline of 2026-10-11.
Scope is the focused follow-up PR described when #39081 was closed:
- extend the Proxy-side BLOB read state with cursor and BLOB type information;
- implement the three seek modes;
- preserve deferred handle resolution for the `0xFFFF` placeholder;
- reject seek for non-stream BLOBs.
@Zhengcy05 you were invited to continue this as a focused follow-up PR against the latest master. If you are still planning to, please say so and I will leave it with you.
Behaviour will be verified against the Firebird server source rather than inferred from the Proxy code alone.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Support op_seek_blob operation in Firebird Proxy [shardingsphere]
Posted by "Zhengcy05 (via GitHub)" <gi...@apache.org>.
Zhengcy05 commented on issue #39051:
URL: https://github.com/apache/shardingsphere/issues/39051#issuecomment-4950273482
`SEEK_BLOB` is already decoded on the protocol side, but the executor does not use the blob handle, seek mode, or offset at all. It only returns a newly generated handle, so the read position is never updated.
The current BLOB read path also keeps the opened content as a single shared in-memory segment and consumes it from the front when `GET_SEGMENT` is called, which means there is no per-open-BLOB cursor to reposition.
My proposed direction is to store read state per opened BLOB handle, implement seek-mode/offset handling there, and return the resulting position in the response. I also want to double-check the BLOB type semantics around stream vs segmented behavior while making that change.
If this direction looks good, I’d like to work on this and submit a PR.
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Support op_seek_blob operation in Firebird Proxy [shardingsphere]
Posted by "terrymanu (via GitHub)" <gi...@apache.org>.
terrymanu closed issue #39051: Support op_seek_blob operation in Firebird Proxy
URL: https://github.com/apache/shardingsphere/issues/39051
--
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: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org