Migrate some calls to ExecuteV1 to V2 transactions

[charnik]

While compiling the engine's SLO log for last week with @NHDaly and @msagarpatel , we noticed a couple of places in RAI's GO SDK where a V1 type of transaction is used where a V2 type of transaction could have been directly used without any extra effort. This concerns places where the SDK compiles a Rel query as a string and submits it via ExecuteV1(). Two such places are the following:

rai-sdk-go/rai/client.go

Line 1546 in 3e6dfd8

return c.ExecuteV1(database, engine, source, inputs, false)

rai-sdk-go/rai/client.go

Line 1560 in 3e6dfd8

return c.ExecuteV1(database, engine, b.String(), inputs, false)

[NRHelmi]

All SDKs are now using v2 protocol. We encourage everyone to update their code to use v2 APIs. We are keeping v1 there for backward compatibility and it will deprecated soon

[NRHelmi]

Sorry I misunderstood the question:
V2 protocol is integrated in all SDKs, we still have some functionalities using the V1 protocol like load csv/json and related models actions. We are working on migrating those functionalities to V2 protocol as well.

[charnik]

Thank you @NRHelmi for confirming!

[billscheidel-rai]

Note: This issue has been migrated to https://relationalai.atlassian.net/browse/RAI-8002.

This link is only accessible to employees of RelationalAI.