ES|QL dense vector field type support #126456

carlosdelest · 2025-04-08T11:24:48Z

Support dense_vector field type. This is the first step to allow kNN queries and having dense_vector as a first class citizen in ES|QL

This allows a mapping that has dense_vector like the following:

{
  "properties": {
    "id": {
      "type": "long"
    },
    "vector": {
      "type": "dense_vector",
      "similarity": "l2_norm"
    }
  }
}

To be retrieved via ES|QL:

FROM dense_vector
| KEEP id, vector
| SORT id

id   | vector
0    | [1.0, 2.0, 3.0]
1    | [4.0, 5.0, 6.0]

For now, just float element types are allowed. There will be a similar work in order to allow for byte and bit element types, but I wanted to review this implementation first to ensure it's in line with what we need.

Both indexed / not indexed types and synthetic source is supported.

Support for CSV tests has been added. For now CSV tests are simple, we can expand on these and also support additional operations on dense_vector field types in subsequent PRs. An integration test has been added to test extensively on different index options and doc storage structure.

dense_vector field type is under a feature flag, as this will require follow up work.

…ctor_support # Conflicts: # x-pack/plugin/esql-core/src/main/java/org/elasticsearch/xpack/esql/core/type/DataType.java # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/ResponseValueUtils.java # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/planner/LocalExecutionPlanner.java

…c fields

…multivalued fields

carlosdelest · 2025-04-08T11:32:30Z

server/src/main/java/org/elasticsearch/index/mapper/BlockDocValuesReader.java

@@ -504,6 +506,80 @@ public String toString() {
        }
    }

+    public static class DenseVectorBlockLoader extends DocValuesBlockLoader {


Added a BlockLoader for dense vectors, that uses FloatVectorValues to retrieve indexed vector data.

carlosdelest · 2025-04-08T11:33:28Z

server/src/main/java/org/elasticsearch/index/mapper/vectors/DenseVectorFieldMapper.java

+        @Override
+        public BlockLoader blockLoader(MappedFieldType.BlockLoaderContext blContext) {
+            if (elementType != ElementType.FLOAT) {
+                throw new UnsupportedOperationException("Only float dense vectors are supported for now");


We can work on this next, creating specific BlockLoaders for Byte and Bit field types.

carlosdelest · 2025-04-08T11:34:15Z

x-pack/plugin/esql/qa/testFixtures/src/main/java/org/elasticsearch/xpack/esql/CsvAssert.java

@@ -145,6 +146,10 @@ private static void assertMetadata(
                    // Type.asType translates all bytes references into keywords
                    continue;
                }
+                if (blockType == Type.DOUBLE && expectedType == DENSE_VECTOR) {
+                    // DENSE_VECTOR is internally represented as a double block


This could potentially change when we support byte and bit element types - we could create the appropriate blocks.

carlosdelest · 2025-04-08T11:35:31Z

x-pack/plugin/esql/qa/testFixtures/src/main/resources/mapping-default-incompatible.json

@@ -63,18 +63,7 @@
            "type" : "keyword"
        },
        "salary_change": {
-            "type": "float",


Changing CSV loading made this a problem, as there were parsing exceptions when trying to index float numeric data into integers. I didn't see a convenient way out of this and decided to remove as this field is not being tested.

If we can keep this unchanged, that will be great, this is a good example of nested fields.

It is just changed for the mapping-default-incompatible mapping, which was created to test some incompatible field mappings that did not include subfields. I'll try to give this another shot but it will require changes to the CSV loader or the dataset 😢

It is just changed for the mapping-default-incompatible mapping, which was created to test some incompatible field mappings that did not include subfields. I'll try to give this another shot but it will require changes to the CSV loader or the dataset 😢

Is it easier if we make another copy of employees's schema and data for dense_vector related tests?

Is it easier if we make another copy of employees's schema and data for dense_vector related tests?

The problem is that changing how the CSV tests load data impacted this dataset. Before this change, multivalues were being uploaded as arrays of strings, which is something we don't want to do for dense_vectors as that is not a format supported on the DenseVectorFieldMapper.

It seemed like too much work to change the actual dataset when that particular field is not actually used in the tests.

I'm open to other solutions here!

@fang-xing-esql are these fields used in other tests somehow?
I see this was actually added by @carlosdelest a while back #117555.
The employees_incompatible index that is set with this mapping is only used in match function/operator tests.
We don't modify any of those tests here, so this looks like a safe change to me.

…support' into feature/esql_dense_vector_support

… values

ioanatia · 2025-04-10T13:27:36Z

...ck/plugin/esql/qa/testFixtures/src/main/java/org/elasticsearch/xpack/esql/EsqlTestUtils.java

@@ -827,6 +829,7 @@ public static Literal randomLiteral(DataType type) {
                    throw new UncheckedIOException(e);
                }
            }
+            case DENSE_VECTOR -> Arrays.asList(randomArray(10, 10, i -> new Double[10], ESTestCase::randomDouble));


Should we actually use randomFloat() and convert the value to double?
The rationale being that if we just use random double values, we might actually end up with something that can't be represented as a float and can't be used to actually index a dense_vector value.

Makes sense - Done in e8878a0

ioanatia · 2025-04-10T13:32:59Z

x-pack/plugin/esql/qa/testFixtures/src/main/resources/dense_vector.csv-spec

+retrieveDenseVectorData
+required_capability: dense_vector_field_type
+
+FROM dense_vector


Can we add more csv tests here with commands we know should be supported 🙈 ?
We have KEEP already, but I'm thinking DROP, RENAME and simple EVALs (EVAL a = dense_vector_field) might be supported already.
I know it should all just work - but for our own peace of mind it would be good to cover them.
Can be a single test that uses a combination of commands we know should be supported already.

I've added one in 93d45fc. I'm not sure what this would catch, as the inner representation of dense_vector is a DoubleBlock and that is extensively tested for other fields.

I'm sure we will keep adding tests once we include arithmetic operators, conversion, etc to dense_vector.

Do we expected that the items in a dense_vector have a fixed order? The reason I'm asking is that a dense_vector looks very like a multi-valued double fields, it is hard to tell whether it is a dense_vector field or a double field with MV from its value looks, and the order of the items in an MV is not guaranteed. I wonder what is the relationship between a double field with MV and a dense_vector.

Do we expect the functions/commands that take multi-valued fields apply to dense_vector? Like those mv_xxx and to_xxx functions, mv_expand, stats by mv_fields etc.?

If I understand it right, dense_vector does not support sort or aggregation, does dense_vector support comparison, does it make sense to dense_vector fields?

Do we expected that the items in a dense_vector have a fixed order?

Yes. It's crucial that the vector dimensions match between different vectors, so they can be compared.

a dense_vector looks very like a multi-valued double fields, it is hard to tell whether it is a dense_vector field or a double field with MV from its value looks

I've used MV as this seemed a supported way of internally representing a double array. From a user perspective, it's a different data type - it's a dense_vector, which will not necessarily be supported on the same functions, and it will always have the same number of dimensions / ordering for a specific mapping.

I wonder what is the relationship between a double field with MV and a dense_vector.

We were thinking on adding a TO_DENSE_VECTOR cast function so users can specific a dense_vector using the MV double syntax:

WHERE knn(field, TO_DENSE_VECTOR([0.1, 0.2, 0.3, ... , 1.0])

Besides that, there should be no relation between the two. They are different data types that have the same representation (an array of elements).

Do we expect the functions/commands that take multi-valued fields apply to dense_vector? Like those mv_xxx and to_xxx functions, mv_expand, stats by mv_fields etc.?

It would probably help to differentiate the two data types if dense_vector fields do not support MV functions.

We can provide support for multivalued functions, but most of them will not make sense in the context of a dense_vector (MV_APPEND, MV_CONCAT, MV_DEDUPE, MV_SORT, MV_SUM). Others can be useful even though they are not necessarily vector related (MV_COUNT, MV_FIRST,MV_MEDIAN, MV_MAX, MV_MIN), but supporting those could confuse ESQL users.

dense_vector does not support sort or aggregation,

Correct.

does dense_vector support comparison, does it make sense to dense_vector fields?

We could support equality. Binary comparisons like greater / less than makes no sense for dense_vector.

Thanks for adding the tests - this is addressed from my POV.
we can follow up on supporting more functions/operators - e.g. equality makes sense to me.

server/src/test/java/org/elasticsearch/index/mapper/vectors/DenseVectorFieldMapperTests.java

fang-xing-esql

Thank you @carlosdelest! At first, it looks to me that the value of a dense_vector field is very similar to a multi-valued double field, so I'm wondering if they work in similar ways, and when do we expect a dense_vector field works differently from the double field in ES|QL? I tried some queries to validate my thoughts, and a lot of times they work very similarly, and sometimes they don't. Here are my observations and you can have a look to see if they make sense. Perhaps I don't see an example of knn query yet, does knn query work on multi-valued double fields? I was looking for where a dense_vector field works differently from a multi-valued double field, and where it is expected to work the same as a multi-valued double field.

mapping

curl -u elastic:password -X PUT "localhost:9200/idx001?pretty" -H 'Content-Type: application/json' -d'
{
  "mappings": {
    "properties": {
      "numericfield": {"type": "double"},
      "mixedfield": {"type": "dense_vector","similarity": "l2_norm"}
    }
  }
}
'

curl -u elastic:password -X PUT "localhost:9200/idx002?pretty" -H 'Content-Type: application/json' -d'
{
  "mappings": {
    "properties": {
      "numericfield": {"type": "double"},
      "mixedfield": {"type" : "double"}
    }
  }
}
'

curl -X PUT "localhost:9200/idx001/_bulk?refresh&pretty" -H 'Content-Type: application/json' -d'
{"index": {}}
{"numericfield": 1,  "mixedfield" : [1.0, 2.0]}
'

curl -X PUT "localhost:9200/idx002/_bulk?refresh&pretty" -H 'Content-Type: application/json' -d'
{"index": {}}
{"numericfield": 2, "mixedfield" : [3.0, 4.0]}
'

queries

+ curl -u elastic:password -v -X POST 'localhost:9200/_query?format=txt&pretty' -H 'Content-Type: application/json' '-d
{
  "query": "from idx00*"
}
'
  mixedfield   | numericfield  
---------------+---------------
null           |2.0            
null           |1.0            

+ curl -u elastic:password -v -X POST 'localhost:9200/_query?format=txt&pretty' -H 'Content-Type: application/json' '-d
{
  "query": "from idx00* | eval x = mixedfield::double"
}
'
{
  "error" : {
    "root_cause" : [
      {
        "type" : "verification_exception",
        "reason" : "Found 1 problem\nline 1:24: Cannot use field [mixedfield] due to ambiguities being mapped as [2] incompatible types: [dense_vector] in [idx001], [double] in [idx002]"
      }
    ],
    "type" : "verification_exception",
    "reason" : "Found 1 problem\nline 1:24: Cannot use field [mixedfield] due to ambiguities being mapped as [2] incompatible types: [dense_vector] in [idx001], [double] in [idx002]"
  },
  "status" : 400
}

+ curl -u elastic:password -v -X POST 'localhost:9200/_query?format=txt&pretty' -H 'Content-Type: application/json' '-d
{
  "query": "from idx001 | mv_expand mixedfield"
}
'
 numericfield  |  mixedfield   
---------------+---------------
1.0            |1.0            
1.0            |2.0            

+ curl -u elastic:password -v -X POST 'localhost:9200/_query?format=txt&pretty' -H 'Content-Type: application/json' '-d
{
  "query": "from idx001 | stats count(*) by mixedfield"
}
'
   count(*)    |  mixedfield   
---------------+---------------
1              |1.0            
1              |2.0            

+ curl -u elastic:password -v -X POST 'localhost:9200/_query?format=txt&pretty' -H 'Content-Type: application/json' '-d
{
  "query": "from idx001 | eval x = mv_sort(mixedfield)"
}
'
  mixedfield   | numericfield  |       x       
---------------+---------------+---------------
[1.0, 2.0]     |1.0            |[1.0, 2.0]     

+ curl -u elastic:password -v -X POST 'localhost:9200/_query?format=txt&pretty' -H 'Content-Type: application/json' '-d
{
  "query": "from idx001 | eval x = mixedfield::string"
}
'
{
  "error" : {
    "root_cause" : [
      {
        "type" : "verification_exception",
        "reason" : "Found 1 problem\nline 1:24: argument of [mixedfield::string] must be [aggregate_metric_double or boolean or cartesian_point or cartesian_shape or date_nanos or datetime or geo_point or geo_shape or ip or numeric or string or version], found value [mixedfield] type [dense_vector]"
      }
    ],
    "type" : "verification_exception",
    "reason" : "Found 1 problem\nline 1:24: argument of [mixedfield::string] must be [aggregate_metric_double or boolean or cartesian_point or cartesian_shape or date_nanos or datetime or geo_point or geo_shape or ip or numeric or string or version], found value [mixedfield] type [dense_vector]"
  },
  "status" : 400
}

+ curl -u elastic:password -v -X POST 'localhost:9200/_query?format=txt&pretty' -H 'Content-Type: application/json' '-d
{
  "query": "from idx002 | eval x= mixedfield::string"
}
'
  mixedfield   | numericfield  |       x       
---------------+---------------+---------------
[3.0, 4.0]     |2.0            |[3.0, 4.0]

fang-xing-esql · 2025-04-12T17:16:23Z

...ck/plugin/esql/qa/testFixtures/src/main/java/org/elasticsearch/xpack/esql/EsqlTestUtils.java

@@ -827,6 +829,7 @@ public static Literal randomLiteral(DataType type) {
                    throw new UncheckedIOException(e);
                }
            }
+            case DENSE_VECTOR -> Arrays.asList(randomArray(10, 10, i -> new Double[10], () -> (double) randomFloat()));


There is a randomDouble() can be used, is the randomFloat() used on purpose here?

this is on purpose, see #126456 (comment)

fang-xing-esql · 2025-04-12T17:21:48Z

x-pack/plugin/esql/qa/testFixtures/src/main/resources/dense_vector.csv-spec

+retrieveDenseVectorData
+required_capability: dense_vector_field_type
+
+FROM dense_vector


Do we expected that the items in a dense_vector have a fixed order? The reason I'm asking is that a dense_vector looks very like a multi-valued double fields, it is hard to tell whether it is a dense_vector field or a double field with MV from its value looks, and the order of the items in an MV is not guaranteed. I wonder what is the relationship between a double field with MV and a dense_vector.

Do we expect the functions/commands that take multi-valued fields apply to dense_vector? Like those mv_xxx and to_xxx functions, mv_expand, stats by mv_fields etc.?

If I understand it right, dense_vector does not support sort or aggregation, does dense_vector support comparison, does it make sense to dense_vector fields?

fang-xing-esql · 2025-04-12T17:24:37Z

x-pack/plugin/esql/qa/testFixtures/src/main/resources/mapping-default-incompatible.json

@@ -63,18 +63,7 @@
            "type" : "keyword"
        },
        "salary_change": {
-            "type": "float",


If we can keep this unchanged, that will be great, this is a good example of nested fields.

carlosdelest · 2025-04-14T08:46:26Z

@fang-xing-esql both dense_vector and a double multivalued field share some common traits:

They are composed as an array of double values
Internal representation uses the multivalue mechanism in Blocks
String representation should work the same way (unless we want it to be different)
Users will use the multivalue format to specify them (potentially converting / casting to a dense_vector type)

They are different as in dense_vector fields:

Values are always ordered
They are not sortable
Most MV_ functions make no sense to operate on dense_vector fields.
dense_vector fields will have specific operations similar to script score existing vector functions.

I think what you observed makes sense for dense_vector fields. We may provide MV_ functions support, but in my mind that would make it confusing from a user perspective. dense_vectors should be treated as a single value, and not a collection of values.

carlosdelest · 2025-04-15T07:21:50Z

@ioanatia @fang-xing-esql I was able to use FLOAT blocks for dense_vector - changed that in cd462b8.

As Ioana noted, we're not publicly exposing float as a type here but dense_vector, so the change is doable as an implementation detail 👍 . Thanks!

…support' into feature/esql_dense_vector_support

ChrisHegarty

I'm happy to see FloatBlocks being used, but they have too much flexibility - all different dims per position and also nulls. Maybe we just need an easy way/utility to assert their correct shape?

.../esql/compute/src/main/java/org/elasticsearch/compute/lucene/ValuesSourceReaderOperator.java

ioanatia

there's an outstanding question from @ChrisHegarty that would be good to address but otherwise LGTM

…mensions

…ctor_support # Conflicts: # x-pack/plugin/esql/qa/testFixtures/src/main/java/org/elasticsearch/xpack/esql/CsvTestsDataLoader.java # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java

carlosdelest · 2025-04-21T11:05:06Z

I'm happy to see FloatBlocks being used, but they have too much flexibility - all different dims per position and also nulls. Maybe we just need an easy way/utility to assert their correct shape?

@ChrisHegarty , I renamed some methods to make clear that we're creating dense vectors instead of floats, and added some checks for them, on c951ee7.

I had to take some back on ba0a6b9, as I can't easily add a new float block builder given the sealed structure of builders. We may have to add a new Block type for dense_vector, maybe as a follow up?

LMKWYT

ioanatia · 2025-04-30T08:19:22Z

x-pack/plugin/esql/qa/testFixtures/src/main/resources/data/dense_vector.csv

@@ -0,0 +1,3 @@
+id:l, vector:dense_vector
+0,    [1.0, 2.0, 3.0]
+1,    [4.0, 5.0, 6.0]


this might be very nitpicky - but can we add another dense_vector value that does not have ordered values?
this might be why we did not caught #126456 (comment) during tests

mvOrdered does not impact retrieval as it's used as an optimization in some cases. But adding unordered data uncovered a small fix that needed to be done to support multivalued style fields: 4b2126e

ioanatia · 2025-04-30T08:25:31Z

...n/esql/src/internalClusterTest/java/org/elasticsearch/xpack/esql/DenseVectorFieldTypeIT.java

+            .field("type", "dense_vector")
+            .field("index", index);
+        if (index) {
+            mapping.field("similarity", "l2_norm");


nit: is it possible to randomize the similarity option? otherwise we could leave this completely out, since it optional?

The problem with that is some similarities normalize the vector values, so what we retrieve back is not what was stored, thus making comparisons difficult. I think we're ok with keeping this simple.

ioanatia · 2025-04-30T08:28:03Z

...n/esql/src/internalClusterTest/java/org/elasticsearch/xpack/esql/DenseVectorFieldTypeIT.java

+
+        try (var resp = run(query)) {
+            assertColumnNames(resp.columns(), List.of("id", "vector"));
+            assertColumnTypes(resp.columns(), List.of("integer", "dense_vector"));


are we missing some assertions here for the values? to at least check that they are not nulls?

That's done in other tests - I started with this test to just check that the field types are retrieved correctly.

ioanatia · 2025-04-30T08:32:41Z

server/src/main/java/org/elasticsearch/index/mapper/BlockSourceReader.java

+
+        @Override
+        public String toString() {
+            return "BlockSourceReader.Floats";


Should this be "BlockSourceReader.DenseVectors"?

++, afe79f7

ioanatia · 2025-04-30T08:39:07Z

server/src/main/java/org/elasticsearch/index/mapper/BlockSourceReader.java

+
+        @Override
+        protected String name() {
+            return "Floats";


Again - just checking if this the value we want to return given that the class is called DenseVectorBlockLoader?

Good catch, I renamed this multiple times but didn't follow on this method. Thanks! afe79f7

…t case

…ctor_support # Conflicts: # server/src/main/java/org/elasticsearch/index/mapper/vectors/DenseVectorFieldMapper.java # x-pack/plugin/esql/qa/testFixtures/src/main/java/org/elasticsearch/xpack/esql/CsvTestsDataLoader.java # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java

carlosdelest · 2025-05-06T08:44:28Z

Closing this PR, as the final approach will imply multiple field types for the different dense_vector element types.

carlosdelest added 14 commits April 7, 2025 11:02

Register dense vector field type

6439422

Add first version of BlockDocValuesReader for dense_vector

c7e48a0

Fixed BlockDocValuesReader to work with all dense_vector types

9e40cd4

Small test fixes

d84c8dd

Fix casting

9ff5ed8

Improve testing to add random indexing, and fix similarity

2754697

Add index = false support

d196be0

Spotless

975b4db

Synthetic source testing

ae9fa5f

Add CSV tests and necessary infra for dense_vector field type

9896adf

Make CSV test loader to use numbers when there are multivalued numeri…

dfa420e

…c fields

Fixed test mapping to avoid parsing errors when numbers are used for …

d983495

…multivalued fields

Avoid non-float dense vector field types for now

5707e25

elasticsearchmachine added the v9.1.0 label Apr 8, 2025

carlosdelest added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) :Analytics/ES|QL AKA ESQL Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch :Search Relevance/Search Catch all for Search Relevance labels Apr 8, 2025

[CI] Auto commit changes from spotless

a8c8a6a

carlosdelest commented Apr 8, 2025

View reviewed changes

carlosdelest added 9 commits April 8, 2025 14:12

Fix test error when checking block loaders

d827c6d

Fix value generation for dense vectors

d8e139d

Merge remote-tracking branch 'carlosdelest/feature/esql_dense_vector_…

0539aff

…support' into feature/esql_dense_vector_support

Fix testing for dense vectors and block loaders

7bbe7ee

Remove dense_vector from CaseTests

7d1f8b7

Provide support in tests for creating constant blocks from collection…

8870fef

… values

Fix test error

ad84f13

Fix unsupported types test

2619fe6

Support synthetic source with non indexed vectors

b23d5a9

ioanatia reviewed Apr 10, 2025

View reviewed changes

carlosdelest added 2 commits April 10, 2025 17:39

Changed randomDouble() for randomFloat() to generate test data

e8878a0

Additional CSV tests

93d45fc

carlosdelest mentioned this pull request Apr 11, 2025

ES|QL dense vector support #125783

Open

23 tasks

Fix class casting

a6b0f6c

fang-xing-esql reviewed Apr 12, 2025

View reviewed changes

carlosdelest added the >non-issue label Apr 14, 2025

Use Float as block type for dense_vector

cd462b8

carlosdelest and others added 4 commits April 15, 2025 10:27

Fix tests

0675a42

[CI] Auto commit changes from spotless

7f95d6a

Fix test

2cff4e7

Merge remote-tracking branch 'carlosdelest/feature/esql_dense_vector_…

efc3fb6

…support' into feature/esql_dense_vector_support

ChrisHegarty reviewed Apr 16, 2025

View reviewed changes

.../esql/compute/src/main/java/org/elasticsearch/compute/lucene/ValuesSourceReaderOperator.java Outdated Show resolved Hide resolved

.../esql/compute/src/main/java/org/elasticsearch/compute/lucene/ValuesSourceReaderOperator.java Outdated Show resolved Hide resolved

ioanatia reviewed Apr 16, 2025

View reviewed changes

carlosdelest added 4 commits April 21, 2025 10:34

Floats are not ordered for dense_vector values

f8741ca

Use dense vector specific methods for creating builders, and check di…

c951ee7

…mensions

Avoid doing checks on dense vectors as we can't cast to BlockBuilder

ba0a6b9

ioanatia reviewed Apr 30, 2025

View reviewed changes

ChrisHegarty approved these changes Apr 30, 2025

View reviewed changes

carlosdelest and others added 4 commits April 30, 2025 19:55

Add CSV tests with unordered data, and fix CSV data retrieval for tha…

4b2126e

…t case

Change source readers name() method

afe79f7

[CI] Auto commit changes from spotless

217ce84

ioanatia approved these changes May 2, 2025

View reviewed changes

carlosdelest closed this May 6, 2025

ES|QL dense vector field type support #126456

ES|QL dense vector field type support #126456

Conversation

carlosdelest commented Apr 8, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ioanatia Apr 10, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

fang-xing-esql Apr 12, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

fang-xing-esql left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

fang-xing-esql Apr 12, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

carlosdelest commented Apr 14, 2025

carlosdelest commented Apr 15, 2025

ChrisHegarty left a comment

Choose a reason for hiding this comment

ioanatia left a comment

Choose a reason for hiding this comment

carlosdelest commented Apr 21, 2025

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

carlosdelest commented May 6, 2025

carlosdelest commented Apr 8, 2025 •

edited

Loading

ioanatia Apr 10, 2025 •

edited

Loading

fang-xing-esql Apr 12, 2025 •

edited

Loading

fang-xing-esql left a comment •

edited

Loading

fang-xing-esql Apr 12, 2025 •

edited

Loading