C0rWin

> @Sayalikukkar This will be a complex epic as the v1.x chaincode lifecycle is embedded in many places. The first thing to do is decompose the work into smaller issues...

> Hello @C0rWin, Let me know if anything is required from my end. Thanks for the suggestion, I will prepare a work plan and then we can decide on how...

> Thanks @C0rWin , that would be great! Perhaps @Sayalikukkar could help on some of the tasks. > > I mentioned @ale-linux because I remember there was some prior design...

Is this is for Update prefixed APIs? I have create a project (https://github.com/C0rWin/buf-gorm-demo/blob/main/protos/entity.proto) to demonstrate the behavour which leads to the panic and to be honest I am not clear...

@fubss Thanks; I believe switching to a more performant k/v is a valuable contribution. However, such changes warrant the need to start with RFC first. Please follow the link and...

https://github.com/erikbern/ann-benchmarks/pull/539, I added a PR pending review to include pgvectorscale

> Hey, are there any updates on when this pr is expected to be done? Would really love to see the comparison with other methods Still pending review... Would love...

@tittuvarghese I'm following up on this pull request for the on-demand reconciliation feature. As @denyeart mentioned in the previous comment, new features that impact component interfaces or introduce new commands...

Given there is no reply or any activity for quite a while, closing it. @tittuvarghese, once you have free cycles to continue working on it, we will gladly review it.

The ([PgVectorScale](https://github.com/timescale/pgvectorscale) extends existing [PgVector](https://github.com/pgvector/pgvector) with [DiskANN](https://github.com/microsoft/DiskANN) index implementation, claiming to have descent improvement over the existing implementation, thought it might be good to include it into ann-benchmark as well.