adityamparikh commented on issue #208: URL: https://github.com/apache/solr-mcp/issues/208#issuecomment-6298846997
**Blocked on MCP Tasks: #274.** An `index-url` transfer, from a URL or a local file, can run for up to `solr.index-url.total-timeout` (default 5 min). It gives no progress feedback, because the stateless HTTP transport cannot send progress notifications, and it can outlast a client's tool-call timeout. The MCP 2026-07-28 spec covers this case with the Tasks extension (`io.modelcontextprotocol/tasks`). Rather than merge a blocking call or add a custom job and status mechanism, this issue waits until the MCP Java SDK and Spring AI support Tasks. #210 stays a draft until then and will be rebased onto `main` from time to time. When it is unblocked, #210's streaming, allow-list and commit-after-complete work carries over, and the tool gains task support: - **Storage:** task state lives in the store Spring AI or the SDK provides. Solr keeps no job record for update requests. - **Progress:** the task's status message reports bytes and documents sent so far. - **Cancel and failure:** a cancelled or failed task says the collection may be partially indexed. Uncommitted documents cannot be rolled back in SolrCloud and become visible at the next commit. - **Concurrency:** the limit of 4 concurrent transfers still applies. A task holds its slot until it reaches a terminal state. The four inline-payload indexing tools are not affected. -- 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]
