pjfanning opened a new pull request, #1553:
URL: https://github.com/apache/pekko-connectors/pull/1553

   ## Summary
   
   Replaces all deprecated OrientDB API usage in the `orientdb` connector 
module.
   
   ## Changes
   
   ### Deprecated classes replaced
   
   | Old (deprecated) | New |
   |---|---|
   | `OPartitionedDatabasePool` | `ODatabasePool` |
   | `ODatabaseDocumentTx` | `ODatabaseSession` |
   | `OSQLSynchQuery` | `OResultSet`-based queries via `client.query(String)` |
   
   ### Details per file
   
   - **`OrientDbSourceSettings.scala`** / **`OrientDbWriteSettings.scala`**: 
pool type changed from `OPartitionedDatabasePool` to `ODatabasePool`.
   - **`OrientDbSourceStage.scala`**: `client` type changed to 
`ODatabaseSession`; non-typed query path now uses `client.query(String)` 
returning `OResultSet` (iterated with `try-finally`); typed path uses 
`oObjectClient.query(String)` + `getUserObjectByRecord`, with 
`OResult.getRecord()` converted from `java.util.Optional` to Scala `Option` via 
`scala.jdk.OptionConverters`; `OObjectDatabaseTx` constructed with 
`asInstanceOf[ODatabaseDocumentInternal]` cast (the actual runtime type 
returned by `ODatabasePool.acquire()`); explicit `setDatabaseOwner` call 
removed since `OObjectDatabaseTx` constructor handles this internally.
   - **`OrientDbFlowStage.scala`**: same pool/client/`OObjectDatabaseTx` 
updates as above.
   - **`OrientDbSpec.scala`** / **`OrientDbTest.java`**: pool construction 
simplified to `new ODatabasePool(dbUrl, username, password)`; all 
`ODatabaseDocumentTx`/`setDatabaseOwner` patterns updated to use 
`ODatabaseSession`/`ODatabaseDocumentInternal`.
   - **`build.sbt`**: removed `fatalWarnings := false` override and its 
obsolete `// note: orientdb client needs to be refactored` comment.
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to