Mark Paluch

> I am using `bootstrap.yaml` for Vault configuration. This is an important detail because in that case, you need to define an override bean (`@Bean ClientFactoryWrapper)`. To do so, create...

Now that our GA release is done, we can finally continue over here.

I'm not convinced of creating a keyspace on startup is a use-case worth supporting. It compares to `CREATE DATABASE` when using JDBC. Databases (keyspaces) should be present when connecting to...

Keyspace creation is typically an operations task similar to SQL databases where the application connects to an existing database instead of creating one. Therefore, this feature is not a first-class...

Taking a step back from the actual problem there is a problem space around database-specific operations that we would like to surface through `Criteria`. Arrays with Postgres is just one...

> However, my concern is that we need to have both approaches Yeah, I think about a general foundation that enables building custom predicates and then, as we progress with...

We iterated on this topic and came up with ideas how we could express dialect-specific operators, conditions, projections and sorting. As initial draft, we could imagine to start with something...

One issue is that MongoDB uses an abstraction that isn't fully applicable to how MongoDB represents paths. Accepting property paths that start with a whitespace is indeed odd, and we...

@qkrtkdwns3410 spring-projects/spring-data-jpa#4109 isn't really addressing what this ticket has been about. Frankly, the ticket has no description so one can easily fill that void with any interpretation, such as you...

> ​The issue content is empty, which can lead to misunderstandings. Internally, we sometimes create tickets as a reminder or follow-up to prior discussions, assuming that we will address them...