added new connector for OpenSearch data source #1335

akuzin1 · 2023-06-15T21:37:08Z

DO NOT MERGE !!! - depends on pending features in OpenSearch sql and sql-jdbc

Description of changes:
This pull request introduces a new OpenSearch connector that implemented the Athena JDBC interface, leveraging the the OpenSearch driver, to enable metadata and data retrieval for the Athena query engine.

Added slight changes to Federation SDK, which should be reviewed and determined whether it is fitting.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

hackett123 · 2023-06-26T18:14:07Z

athena-federation-sdk/src/main/java/com/amazonaws/athena/connector/lambda/data/BlockUtils.java

@@ -849,6 +849,12 @@ else if (value instanceof Integer) {
                    if (value == null) {
                        float4Writer.writeNull();
                    }
+                    else if (value instanceof java.lang.Integer) {


do these changes have implications for any of the other connectors?

They should not. I used similar structure to other data types in BlockUtils::writeSimpleValue, checking if value is of specific instance helps with writing value to block, doesn't change core behavior.

hackett123 · 2023-06-26T18:19:32Z

...na-federation-sdk/src/main/java/com/amazonaws/athena/connector/lambda/data/FieldBuilder.java

@@ -42,6 +42,7 @@ public class FieldBuilder
    private final boolean nullable;
    //Using LinkedHashMap because Apache Arrow makes field order important so honoring that contract here
    private final Map<String, Field> children = new LinkedHashMap<>();
+    private final Map<String, FieldBuilder> nestedChildren = new LinkedHashMap<>();


would you mind explaining this addition? isn't nesting already available because we can have children which are Fields, and those children can themselves have children, etc? or does the existing children behavior not actually work like that?

after reading through the rest of the PR, let me know if my understanding is correct.

if i have a field like:

"topObj": { "innerObj": { "intField": 1, "strField": "asdf" }, "int": 5 }

then opensearch will send back each of these fields as their own columns, and our result set will have this:
topObj.int
topObj.innerObj.intField
topObj.innerObj.strField

so the reason for this new nested children field and it's corresponding logic with OpensearchUtils class is so you can say createNestedStruct andd pass in topObj.innerObj.intField (for example), have it find the struct topObj, and continue to build to the struct definition for topObj?

Yes that's correct. It makes it more intuitive to make complex nested fields in my opinion.

hackett123 · 2023-06-26T18:41:37Z

...a-federation-sdk/src/main/java/com/amazonaws/athena/connector/lambda/data/SchemaBuilder.java

@@ -89,6 +89,18 @@ public SchemaBuilder addStructField(String fieldName)
        return this;
    }

+    /**
+     * Adds a new Nested STRUCT Field to the Schema as a top-level Field.


So this is for nested structs, did we not support nested structs in any connectors before? Does this impact functionality in any existing connectors?

No, I don't believe that existing connectors should be impacted, its independent. We do support nested structs in other connectors. The added functions were kind of tailored to OpenSearch use case and I thought it made sense to expand the SchemaBuilder functionality.

hackett123 · 2023-06-26T18:43:17Z

athena-jdbc/src/main/java/com/amazonaws/athena/connectors/jdbc/manager/JdbcRecordHandler.java

                readRecordsRequest.getSplit().getProperties());
        try (Connection connection = this.jdbcConnectionFactory.getConnection(getCredentialProvider())) {
-            connection.setAutoCommit(false); // For consistency. This is needed to be false to enable streaming for some database types.
+            if (this.getAutoCommit().isPresent()) {


not sure I understand if this modification is adding any value. Are you expecting getAutoCommit() to not always return false in the future?

oh i see, in the opensearch record handler you have it return Optional.empty(). But is there a reason to even have that as an optional wrapping around a boolean, instead of it just being a boolean?

Yes, so the reason it's an Optional is because, the presence of a value does not signify true, we want to maintain the original behavior.
I can go back and do additional testing, however, we did not want to setAutoCommit for the OpenSearch driver.

hackett123 · 2023-06-26T18:43:47Z

athena-jdbc/src/main/java/com/amazonaws/athena/connectors/jdbc/manager/JdbcRecordHandler.java

@@ -168,8 +185,9 @@ public void readWithConstraint(BlockSpiller blockSpiller, ReadRecordsRequest rea
                    rowsReturnedFromDatabase++;
                }
                LOGGER.info("{} rows returned by database.", rowsReturnedFromDatabase);
-
-                connection.commit();
+                if (this.getAutoCommit().isPresent()) {


also not sure what this adds.

We only need to commit connection if we setAutoCommit, and we don't need to do that for the OpenSearch driver.

hackett123 · 2023-06-26T21:19:51Z

...arch/src/main/java/com/amazonaws/athena/connectors/opensearch/OpensearchMetadataHandler.java

+                // update schema from null because Opensearch doesn't have schema but change later
+                // resultSet.updateString("TABLE_SCHEM", databaseName);
+
+                // Temporary in schemaName 
+                list.add(getSchemaTableName(resultSet, databaseName));


having a hard time understanding the comments here

Left over comments. Will get rid of.

hackett123 · 2023-06-26T21:21:45Z

...arch/src/main/java/com/amazonaws/athena/connectors/opensearch/OpensearchMetadataHandler.java

+        Pattern pattern = Pattern.compile(DATA_STREAM_REGEX);
+        Matcher matcher = pattern.matcher(tableName);
+        if (matcher.find()) {
+            tableName = matcher.group(2);
+        }


can you explain this? I thought you mentioned data streams are not yet supported. Also, let's avoid magic numbers or add an example in the comment for what this looks like to explain why we match on group 2

Yes will provide embedded example for reference.
But to give a brief explanation here is that a data stream lets you store time series data across multiple indices while giving you a single named resource for requests. The multiple indices that correlate with one data stream have the following naming convention: .ds-<data-stream>-<generation> where generation is a six-digit, zero-padded integer.
Therefore, instead of populating the many indices correlating to a single data stream, I only want to display the one data stream and I achieve that through pattern matching.

...search/src/main/java/com/amazonaws/athena/connectors/opensearch/OpensearchRecordHandler.java

hackett123 · 2023-06-26T21:32:36Z

...search/src/main/java/com/amazonaws/athena/connectors/opensearch/OpensearchRecordHandler.java

+        PreparedStatement preparedStatement = jdbcSplitQueryBuilder.buildSql(jdbcConnection, null, null, tableName.getTableName(), schema, constraints, split);
+
+        // Disable fetching all rows.
+        preparedStatement.setFetchSize(10000);


let's put this in a constant.

what happens if the input query has over 10k results?

Setting fetch size Gives the JDBC driver a hint as to the number of rows that should be fetched from the database when more rows are needed for ResultSet objects generated by this Statement.
So what this really controls is the number of network calls, as well as enforces pagination so that SQL Plugin uses v2 instead of legacy engine. Otherwise legacy version only returns 200 rows per table.

athena-opensearch/src/main/java/com/amazonaws/athena/connectors/opensearch/OpensearchUtils.java

macohen · 2024-01-23T23:38:15Z

What’s the sql/jdbc feature that’s needed from opensearch to bring this closer to merging? Also, are there any performance comparisons done between sql/jdbc vs using a Java or another client?

akuzin1 · 2024-01-24T23:03:51Z

Hi, @macohen! We were waiting for the implementation of shard partitioning, which would allow to parallelize the fetching of data with the JDBC driver. Currently the connector implements a single partition solution, which resulted in performance regression compared to current connector version.
I had opened an feature request and was working with the OpenSearch team to track item, however, due to shifting priorities the item got backlogged.

macohen · 2024-02-05T17:39:51Z

@akuzin1 can you link to the feature request here, please?

akuzin1 · 2024-02-05T19:14:04Z

@macohen linking issue here fromopensearch-project/sqlrepository

akuzin1 force-pushed the OpenSearchConnector branch from 7a3a4ad to 7053f9e Compare June 19, 2023 00:43

hackett123 reviewed Jun 26, 2023

View reviewed changes

akuzin1 force-pushed the OpenSearchConnector branch from 0086dcc to f66cc58 Compare June 29, 2023 15:02

added new connector for OpenSearch data source

ed2d591

akuzin1 force-pushed the OpenSearchConnector branch from f66cc58 to 42ac46f Compare July 13, 2023 19:55

Refactoring, addressing Michaels comments

334e9d7

akuzin1 force-pushed the OpenSearchConnector branch from 42ac46f to 334e9d7 Compare July 18, 2023 20:18

AbdulR3hman added glue_connections_adoption Moving properties from lambda to Glue Connections for better management of connections. and removed glue_connections_adoption Moving properties from lambda to Glue Connections for better management of connections. labels Aug 7, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

added new connector for OpenSearch data source #1335

added new connector for OpenSearch data source #1335

akuzin1 commented Jun 15, 2023 •

edited

Loading

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023

hackett123 Jun 26, 2023

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023

hackett123 Jun 26, 2023

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023 •

edited

Loading

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023

hackett123 Jun 26, 2023

akuzin1 Jun 27, 2023

macohen commented Jan 23, 2024

akuzin1 commented Jan 24, 2024

macohen commented Feb 5, 2024

akuzin1 commented Feb 5, 2024

added new connector for OpenSearch data source #1335

Are you sure you want to change the base?

added new connector for OpenSearch data source #1335

Conversation

akuzin1 commented Jun 15, 2023 • 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

akuzin1 Jun 27, 2023 • 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

macohen commented Jan 23, 2024

akuzin1 commented Jan 24, 2024

macohen commented Feb 5, 2024

akuzin1 commented Feb 5, 2024

akuzin1 commented Jun 15, 2023 •

edited

Loading

akuzin1 Jun 27, 2023 •

edited

Loading