-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Distribution settings hardcoded to OFF? #103
Comments
The client documentation you are referring to is not applicable to this driver implementation. The features provided by this client are described solely in |
We want to leverage statement routing because we have a scale-out HANA system with several nodes and we have partitioned tables, where each partition is spread across each one of these nodes evenly with some metadata tables being replicated across all nodes. We are already executing prepared queries which is one of the prerequisites to being able to do statement routing. We would like to make our queries more efficient by executing in the node where the data resides instead of having HANA perform networking operations to move data across nodes. |
Thanks a lot for the additional information! |
Hi Stefan, Thanks for the response. I might have the wrong understanding of this feature but I believe that the HANA DB does all the work, the only thing that needs to be done from the client side is to pass a value on the DISTRIBUTION parameter. Do you see this as a major change that needs to be included in version 2 (date, TBD) or could this be implemented sooner? |
Hello @kermitbravo,
If so, I guess we would be able to do the implementation earlier. But according to the information you did share above
the client library is in charge to select the right endpoint after a prepare would indicate which index server to be used. Currently go-hdb does have a 1:1 relationship of a go sql connection / db backend connection and the control of which connection is used for a statement is solely with go sql connection pooling logic (exceptions are transactions or the usage of dedicated connections via the sql Conn object). |
I agree that to enable statement routing there might be additional work here but to at least enable ClientDistributionMode Connection (round-robin, which is better than nothing) the change would be less involved? |
Sorry for the late answer! |
That would be great, thanks Stefan. |
We are trying to enable statement routing on prepared statements using the golang HANA db client but there's no obvious way to set the Connection Option Distribution to ALL or STATEMENT.
SAP Documentation
https://help.sap.com/docs/SAP_HANA_PLATFORM/0eec0d68141541d1b07893a39944924e/8d61ae225ae44b0bab2fb2285009f68d.html
STATEMENT ROUTING
https://launchpad.support.sap.com/#/notes/2079372
Default option for CoClientDistributionMode set to OFF.
https://github.com/SAP/go-hdb/blob/main/driver/connection.go#L1297
The text was updated successfully, but these errors were encountered: