vec-379 Support AVS 0.11.x

[dwelch-spike]

• Adds number of vectors and vertices in the index list/get methods.
• Allows for infinite cache expiration using -1
• Allow for caching vector records
• Allow toggling vector integrity checks
• Make multiple fields optional
• Rename multiple fields

Summary of proto changes and their implications…

Adds…

indexStatusResponse

    indexHealerVectorRecordsIndexed

    indexHealerVerticesValid

hnswParams

    recordCachingParams

    enableVectorIntegrityCheck

indexUpdateParams

    recordCachingParams

    enableVectorIntegrityCheck

HnswBatchingParams

    maxReindexRecords

    reindexInterval

Changes the type of…

HnswCachingParams

    expiry from uint64 to int64 (this BREAKS the grpc protocol making this api version incompatible with older clients and older servers)

Renames (these are all BREAKING changes for applications consuming the go client)

HnswIndexUpdate

    cachingParams → indexCachingParams

HnswParams

    cachingParams → indexCachingParams

HnswBatchingParams

    maxRecords → maxIndexRecords

    interval → indexInterval

Makes Optional (these are all BREAKING changes for applications consuming the go client)

PutRequest

    WriteType

ProjectionFilter

    ProjectionType

IndexDefinition

    IndexType

    VectorDistanceMetric

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.08%. Comparing base (e6d6218) to head (4db9cb3).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
+ Coverage   92.57%   93.08%   +0.50%     
==========================================
  Files           7        7              
  Lines        2007     2010       +3     
==========================================
+ Hits         1858     1871      +13     
+ Misses        116      109       -7     
+ Partials       33       30       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rahul-aerospike]

Is there a reason we are committing generated proto files to the repository? Since this is a compiled language, I would assume it's possible to generate the proto files during the artifact generation process, rather than committing them. @dwelch-spike

[dwelch-spike]

Is there a reason we are committing generated proto files to the repository? Since this is a compiled language, I would assume it's possible to generate the proto files during the artifact generation process, rather than committing them. @dwelch-spike

@rahul-aerospike It's so that consumers of this library can use it more easily. In Golang, libs aren't built into artifacts like wheels in Python, instead source code is pulled in directly with the go get command. With the generated files in the repo, the code will work out of the box

[rahul-aerospike]

@dwelch-spike Got it, that makes sense. In a future release, it might be better to organize the proto files into a separate directory from the generated files.

[rahul-aerospike]

Every thing else looks good to me. Please wait for yevgeny's approval before merging, if possible.