IKV integration - new online store for feature serving - docs.inlined.io

[pushkarmoi]

Description

This PR adds https://github.com/inlinedio/ikv-store as a new online store for feature form.
IKV client library: go get github.com/inlinedio/ikv-store@latest

OnlineStore and OnlineStoreTable interfaces have been implemented ie. Create/Get/DeleteTable and then Set/Get operations on individual tables.

Pending (next PR): docs/markdown changes to add IKV here: https://docs.featureform.com/inference-online-stores

New Online Store plugin

No open issue

make test_online provider=ikvonline

--- PASS: TestOnlineStoreIKV (35.32s)
    --- PASS: TestOnlineStoreIKV/CreateGetTable_IKV_ONLINE (0.00s)
    --- PASS: TestOnlineStoreIKV/TableAlreadyExists_IKV_ONLINE (0.00s)
    --- PASS: TestOnlineStoreIKV/TableNotFound_IKV_ONLINE (0.00s)
    --- PASS: TestOnlineStoreIKV/SetGetEntity_IKV_ONLINE (10.07s)
    --- PASS: TestOnlineStoreIKV/EntityNotFound_IKV_ONLINE (0.00s)
    --- PASS: TestOnlineStoreIKV/MassTableWrite_IKV_ONLINE (13.29s)
    --- PASS: TestOnlineStoreIKV/TypeCasting_IKV_ONLINE (10.20s)

Type of change

New infrastructure provider integration (online store)

Does this correspond to an open issue?

No open issue

Select type(s) of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have fixed any merge conflicts

[anthonylasso]

This is awesome @pushkarmoi, the dev team will give this a look soon and give you any feedback!

[anthonylasso]

Solid stuff, giving the initial approve and I'll get with the team for the next merge step.

(shouldn't take long, just logistical stuff)

[pushkarmoi]

Solid stuff, giving the initial approve and I'll get with the team for the next merge step.

(shouldn't take long, just logistical stuff)

No worries, thanks a lot for the review!

[pushkarmoi]

Solid stuff, giving the initial approve and I'll get with the team for the next merge step.

(shouldn't take long, just logistical stuff)

Some questions, @anthonylasso when you get a chance -
Also cc @sdreyer

1. I noticed there is a hook to update configs of online-stores (?at runtime?)

   featureform/metadata/metadata.go

   Line 1349 in 36442e5

   func (resource *providerResource) isValidConfigUpdate(configUpdate pc.SerializedConfig) (bool, error) {

   
   I didn't understand it fully - and have not allowed any config changes for IKV. What are the implications?

2. The register method for IKV has the following signature. The user needs to specify a "mount point" on the local container/host where they spin up the provider - where all IKV data will be stored (its an embedded database). I'm unsure about which directory the end user can use for this purpose (considering this runs inside featureform docker)

ikv = ff.register_ikv(
            name="ikv-quickstart",
            store_name="ikv-store-name",
            account_id="ikv-account-id",
            account_passkey="ikv-account-passkey",
            mount_dir="/path/to/mount_dir",
        )