Entity/table for connection pooling?

[KnowZero]

Entity/table for connection pooling?

[ohsayan]

Thanks for bringing this up.

1. The connection pool (sync/async) is simply a collection of connections to the Skytable server. Since the entity is local to every connection, the only way to do it currently is by getting a connection from the pool and switching the entity, like you have noted

2. And you are correct: there is a lookup penalty. This was actually discussed sometime back on our chat channel. The best way to do this is by redefining what the Connection structure looks like to include an entity field (possibly a boxed slice):

      pub struct Connection {
          entity: (Ks, Tbl),
          ...
      } 

   So, whenever you attempt to switch, it'll check whether you're already using that entity. This is far better than sending a request to the server only to find out that you're already using the same entity

3. Assigning a number of connections to a given entity actually seems like a very good idea. I think we can discuss this further. Although, you can always create multiple pools for every entity that you plan to access, but I agree, having library-level support would be very convenient

4. Regarding the Docker image, can you please open an issue here? If you check this post on planned changes to Docker images it can explain some things, and what we plan to do ahead

[MuhtasimTanmoy]

What would be the high-level design for this issue?