We need a solution that everyone can use easily. Ideally, contributors to the rest of Calcite - say Calcite core - should not have to spend extra effort, or experience any extra delay or flakiness, in order to verify that they have not broken the Redis adapter.
The nearest example we have today is the Druid adapter. Stamatis spent considerable time recently [1] to set up a container for Druid, document how to use it, and enable it in CI. Someone could do the same for Redis, preferably using the same container technology. Julian [1] https://issues.apache.org/jira/browse/CALCITE-4278 On Sat, Oct 17, 2020 at 12:46 AM Tugdual Grall <[email protected]> wrote: > > Hello, > > I am new to the Calcite (at least trying to contribute - I did use it > indirectly a lot in Apache Drill ) > > I would like to enrich the Redis adapter (or create a new one) to support > RediSearch ( http://redisearch.io ) since it provides richer features such > as secondary indexing, querying and aggregations on data located in Redis. > > What is the best way to run tests? > I see that the current Redis tests are using a fake implementation, same > for Mongo... > > RediSearch does not have such an implementation (and same for other modules > Graph, JSON, ..) > > Are we "allowed" to use containers in the tests, for example using > TestContainers ( https://www.testcontainers.org/ ) ? > > If not can you point me to the proper way to run tests when a mock server > does not exist? > > Thanks > Tug
