[
https://issues.apache.org/jira/browse/SOLR-16461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626684#comment-17626684
]
Jason Gerlowski edited comment on SOLR-16461 at 10/31/22 4:41 PM:
------------------------------------------------------------------
To copy a bit of discussion about this that happened on the PR:
bq. You've got a really keen eye for all the stuff that doesn't work yet! 😛
You're right - we don't currently have a way to get those requestHandler-level
settings forwarded to the corresponding v2 API. Definitely something I hope to
fix sooner rather than later. I spiked out a solution awhile back but it was
pretty hacky. If you're interested in digging into that some, definitely lmk
and we can get a JIRA filed and work on it together.
Long story short: it's definitely a gap we have with our JAX-RS v2 APIs today,
but it's on my radar and something I'm hoping to fix soon. The simplest and at
least slightly idiomatic approach would be to add a Jersey request-filter to
tunnel this information in (hopefully in a more strongly-typed fashion than the
traditional NamedList), but there are few options. Anyway, definitely a
discussion for a follow-up ticket.
----
EDIT:
Hmm, just realized that this might be a bit of a blocker in a way that I didn't
realize until now.
i.e. if Backup uses any of the properties that typically get configured in
solrconfig.xml, it's hard for it to do its job without those.
It'd be trivial to just hardcode in a default, but there's a real risk we'd
forget about it later on when we _do_ have a solution for getting these config
values. If it's a hard blocker, we can put a comment nearby that mentions
"SOLR-16513" (a ticket I created just now to fix this gap), but it's definitely
a hacky workaround.
I'll prioritize a PR to fix this gap on the config side of things.
was (Author: gerlowskija):
To copy a bit of discussion about this that happened on the PR:
bq. You've got a really keen eye for all the stuff that doesn't work yet! 😛
You're right - we don't currently have a way to get those requestHandler-level
settings forwarded to the corresponding v2 API. Definitely something I hope to
fix sooner rather than later. I spiked out a solution awhile back but it was
pretty hacky. If you're interested in digging into that some, definitely lmk
and we can get a JIRA filed and work on it together.
Long story short: it's definitely a gap we have with our JAX-RS v2 APIs today,
but it's on my radar and something I'm hoping to fix soon. The simplest and at
least slightly idiomatic approach would be to add a Jersey request-filter to
tunnel this information in (hopefully in a more strongly-typed fashion than the
traditional NamedList), but there are few options. Anyway, definitely a
discussion for a follow-up ticket.
----
> Create v2 equivalent of v1 ReplicationHandler 'BACKUP'
> ------------------------------------------------------
>
> Key: SOLR-16461
> URL: https://issues.apache.org/jira/browse/SOLR-16461
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Affects Versions: 9.1
> Reporter: Sanjay Dutt
> Priority: Major
> Labels: V2
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> A backup API for user manager cluster or single node installation has no v2
> equivalent. This ticket is used to track changes that will be made to add the
> v2 API for the 'backup'.
> Â
> Â
> Â
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]