exceptionfactory commented on code in PR #9640:
URL: https://github.com/apache/nifi/pull/9640#discussion_r1924376503


##########
nifi-extension-bundles/nifi-standard-services/nifi-database-dialect-service-api/src/main/java/org/apache/nifi/database/dialect/service/api/QueryStatementRequest.java:
##########
@@ -0,0 +1,31 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.database.dialect.service.api;
+
+import java.util.Collection;
+import java.util.Optional;
+
+/**
+ * Query extension of Statement Request with additional properties for SELECT 
statements
+ */
+public interface QueryStatementRequest extends StatementRequest {
+    Optional<String> derivedTable();
+
+    Collection<QueryClause> queryClauses();

Review Comment:
   Thanks for the feedback. In the initial stage of refactoring, I considered 
the possibility for other types of query clauses. As the implementation played 
out, I agree that switching from the collection to optional properties for 
whereClause and orderByClause would be easier to follow and maintain. I will 
make adjustments and push an updated version.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to