nddipiazza opened a new pull request, #2505: URL: https://github.com/apache/tika/pull/2505
## Summary This PR upgrades Apache Ignite from 2.16.0 to 3.1.0 in the tika-pipes-config-store-ignite module. ## Changes Made ### Core Upgrade - **Upgraded dependencies**: ignite-core 2.16.0 → ignite-runner 3.1.0 - **Migrated configuration**: From IgniteConfiguration API to HOCON-based config files - **Updated API usage**: Migrated from IgniteCache to new KeyValueView API - **Fixed DTO mapping**: Updated ExtensionConfigDTO to use Ignite 3.x Mapper annotations ### Server & Integration - **Simplified IgniteStoreServer**: Removed async complexity, now synchronous embedded mode - **Fixed EmitHandler**: Added null check for NO_EMIT scenario to prevent NPE - **Updated gRPC proto**: Added emitter_id field to FetchAndParseRequest - **Updated TikaGrpcServerImpl**: Proper lifecycle management for IgniteStoreServer ### Testing & CI - **Added e2e tests to parent build**: tika-e2e-tests module now integrated - **Local server mode for CI**: Tests run without Docker by default (faster, more reliable) - **Fixed resource leaks**: Proper gRPC channel cleanup in tests - **Added JVM flags**: Required --add-opens flags for Java 17+ compatibility - **Disabled enforcer**: For e2e tests due to Ignite 3.x transitive dependency conflicts ## Test Results ✅ **11/11 unit tests passing** in tika-pipes-config-store-ignite ✅ **E2E test passing** - processes documents successfully ✅ **No resource leaks** - proper cleanup verified ✅ **BUILD SUCCESS** locally ## Breaking Changes None - API remains backward compatible from user perspective ## CI Configuration Tests use local server mode by default: - Property: `tika.e2e.useLocalServer=true` - Override with `-Dtika.e2e.useLocalServer=false` to use Docker Fixes apache/tika#TIKA-4606 -- 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]
