support named vectors / collections with multiple vectors

[danielsig727]

Hello,

CMIIW, from the code, the connector doesn't seem to support collections with named vectors . Are there any plans to support it? 🙏 thanks

[Anush008]

This feature should be great to go with V2 which is in the works.
#8

Will do.

[Anush008]

@danielsig727, you can add named vectors like so in V2 with this commit.

#option("vector_name", SOME_VECTOR_NAME).

There's some dep build issues that need resolving. Should be out after that.

[danielsig727]

@Anush008 thanks! what about multiple vectors?
maybe it'd be nice if the interface is like:

.option("embedding_field", "field1,field2,field3")
.option("vector_name", "vec_name1,vec_name2,vec_name3")

So it doesn't break existing code

[Anush008]

Then it would be better to pass the names as an array or a string(single)

Can take that up once the build issue is resolved.

[Anush008]

Plus, there can be breaking changes. Since it's a major bump.

We're moving from REST to GRPC(Different ports).

[danielsig727]

ok, i'm good with either way
looking forward to it! 😄

[Anush008]

The build issue in V2 seems to be caused by an indirect dep. I'm on leave next week. Will tackle this when I return.

[Anush008]

We've been having a conversation regarding the V2 release at #6.

[arkodoescode]

@Anush008 any updates on this? Will this be released with V2?

[Anush008]

@a-bhattacharya, the dependency blocker for V2 still persists.

I think I'll add named vector support to V1.

[Anush008]

@a-bhattacharya, please refer to #6 (comment).