Hi,
I fully agree with what was said before. but as a Solr newbie that gets
lost quite a lot of times in jiras and PRs I want to say asking the list
for guidance should be a good way to go about clarifying some peculiar
implementation details.
Out of curiosity I dug up some links:
- Jira
Hi Paul,
As a technique to inquire about "why" questions, I sometimes find the
original JIRA issue and/or PR and ask there. It may be a years-old
issue/PR but I personally think nothing of it -- it's practical as it pings
relevant people watching vs. a shot in the dark about an obscure matter.
Sorry for the delay, I had to collect this information from the team.
As you said: Crave doesn't need to know the commit history, it just needs
enough information from git to be able to reproduce the filesystem state on to
the remote side without having to do a full rsync.
We have to account
Hi,
Thanks for reporting. Sounds you have enough supporting proof to create a JIRA
(bug) issue, and we can continue discussion there.
Jan
> 22. aug. 2023 kl. 21:51 skrev Paul McArthur
> :
>
> Hi all,
>
> I’m creating a cluster singleton plugin and have found an issue with the
> lifecycle
Hi all,
I’m creating a cluster singleton plugin and have found an issue with the
lifecycle management of the singleton if the plugin is updated via the API.
When the /cluster/plugin api is called with an update payload, the
ClusterSingletons.modified method is called, which adds the new plugin
Hi all,
SOLR-16876 is about moving bin/solr auth command argument parsing into Java
code.
I’ve put up a draft PR to start this effort, but run on some challenges in my
shell scripting skills on how best to port some of the directory parsing logic
that is in the shell script over to Java
