davsclaus opened a new pull request, #3181:
URL: https://github.com/apache/camel-kamelets/pull/3181

   Two small follow-ups to #3170.
   
   ### `solr-source` uses the `SEARCH` operation
   
   `solr-source` sets `CamelSolrOperation=QUERY`. On every poll, Camel 4.24 
logs that `QUERY` "is going to be deprecated in future versions of camel-solr" 
and says to use `SEARCH`. The template now uses `SEARCH`.
   
   Tested against Solr 9.10.1 in Docker, with the query `status_s:new` on 3 
documents:
   
   | Kamelet | Result |
   |---|---|
   | From `main` (`QUERY`) | Returns `p1` and `p2`, and logs the deprecation 
warning on every poll |
   | From this PR (`SEARCH`) | Returns the same response, with no warning |
   
   ### `aws-redshift-sink` and `aws-redshift-source` take `connectionProperties`
   
   This is the same option that #3176 adds to the PostgreSQL, MySQL and MariaDB 
Kamelets. It is a string of `name=value` pairs separated by `;`, which the 
commons-dbcp2 data source passes to the Amazon Redshift JDBC driver. When it is 
not set, nothing changes. #3176 left these Kamelets out, because they could not 
be tested against Redshift.
   
   Tested as far as a local PostgreSQL 17 allows. The Redshift driver speaks 
the PostgreSQL protocol up to the login:
   
   | Case | Result |
   |---|---|
   | Option unset | `The server does not support SSL`: the driver insists on 
TLS, as before |
   | `connectionProperties: ssl=false` | Gets past TLS and logs in, so the 
setting reaches the driver |
   
   After the login, PostgreSQL rejects a startup parameter specific to Redshift 
(`driver_version`), so reading rows needs a real Redshift.
   
   `./mvnw clean install` passed twice, the first time with `-DskipTests`.
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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