[ 
https://issues.apache.org/jira/browse/TIKA-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046424#comment-18046424
 ] 

Nicholas DiPiazza commented on TIKA-4583:
-----------------------------------------

h3. Update: Added init() call in AbstractComponentManager

I've pushed an important fix to ensure {{ConfigStore.init()}} is actually 
called when component managers are created.

*Changes:*
* Modified {{AbstractComponentManager}} constructor to call 
{{configStore.init()}} before using the store
* Added proper exception handling (wraps in RuntimeException if init fails)
* All existing tests pass with this change

This ensures that:
* {{InMemoryConfigStore}} continues to work (uses default no-op init)
* {{IgniteConfigStore}} will properly initialize its Ignite instance and cache
* Any future ConfigStore implementations requiring initialization will work 
correctly

The PR has been updated with this fix.

> Add Apache Ignite ConfigStore implementation
> --------------------------------------------
>
>                 Key: TIKA-4583
>                 URL: https://issues.apache.org/jira/browse/TIKA-4583
>             Project: Tika
>          Issue Type: Sub-task
>            Reporter: Nicholas DiPiazza
>            Priority: Major
>
> h3. Overview
> Create an Apache Ignite-based implementation of the ConfigStore interface to 
> enable distributed configuration storage for Tika Pipes clustering.
> h3. Implementation Details
> * Create new Maven sub-module: {{tika-pipes/tika-pipes-ignite-config-store}}
> * Implement {{IgniteConfigStore}} class that uses Apache Ignite cache for 
> distributed storage
> * Add {{init()}} method to {{ConfigStore}} interface for initialization 
> support
> * Provide configuration options for Ignite cluster connection
> * Ensure thread-safety and proper error handling
> h3. Technical Requirements
> * Maven module structure following Tika conventions
> * Proper Apache license headers
> * Unit tests for the implementation
> * Integration tests for distributed scenarios
> * Documentation in JavaDoc
> * Update parent pom.xml to include new module
> h3. Dependencies
> * Apache Ignite client libraries
> * Serialization support for ExtensionConfig objects
> h3. Acceptance Criteria
> * {{ConfigStore}} interface has {{init()}} method
> * {{IgniteConfigStore}} implementation passes all ConfigStore tests
> * New module builds successfully with {{mvn clean install}}
> * Documentation explains configuration options
> * Integration with existing Tika Pipes clustering infrastructure



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to