With regards to the API, I'm tempted to hide the ovsdb.Operation, make the transaction and return a list of elements. @dave-tucker , do you think Select operations are likely to be batched into larger transactions?

@amorenoz hmmm. I don't think it's likely to be batched, but for to be consistent with other operations it would be better to have it return []ovsdb.Operation. That way the client has total control over how things are run.

Just wanted to know, is there an estimate by when this feature may be added.

@dave-tucker @amorenoz It would help if you could let me know, is there a group where doubts are discussed? I tried to join the slack channel mentioned in the readme but it asks to contact the workspace administrator (if not from redhat/nvidia).
Thanks

Hi @rutuja-clusters , sorry I have missed your comment. I don't understand why you are not being able to join the slack channel. It's part of the ovn-org.slack.com. I'll ask around to see who can help here.

As for the ETA for this, we haven't had much push on this feature because of the possibility of using WhereCache. I don't know what the plans are on this. Any idea @flavio-fernandes @jcaamano ?

There are no plans that I am aware of about this topic.

It should be straight forward enough to have a Select operation. I guess we would need to add as well an additional utility method able to parse the models from the results?

Also the added support of conditional monitoring might alleviate some of the initial concerns @amorenoz had in the issue opener.

@jcaamano any updaes of this issue? Select operation is very useful in some sceneries.

@yuyang0 no updates. Would you be willing to contribute a PR towards this? Otherwise it is just a matter of finding the time to do it.