Wed, 27 Oct 2021 at 12:04, Ishan Chattopadhyaya
wrote:
>
> Alex, these seem to be issues with config API (and should be solved), while
> this discussion is about v2 version of all APIs. What is the relevance here?
>
> On Wed, 27 Oct, 2021, 9:24 pm Alexandre Rafalovitch,
> wrote:
I feel that the summary of my umbrella case (SOLR-14795) qualifies for this:
"
General issues with output being materialized schema:
* parameters have already been resolved and are not indicated
* empty keys may not be output (e.g. dataDir)
* default parameters will be output that are not in solrc
I felt that V2's lack of support for defaults was a serious architectural
issue that is hard to just close eyes on.
Regards,
Alex
On Tue., Oct. 26, 2021, 3:17 p.m. Eric Pugh, <
ep...@opensourceconnections.com> wrote:
> I’d very much like to see this as well.
>
> I’ve been thinking that I woul
I did some analysis work on that a while ago, though now I realized I
did not mark it well with V2 perhaps.
https://issues.apache.org/jira/browse/SOLR-14795
Regards,
Alex.
On Mon, 25 Oct 2021 at 16:12, Jason Gerlowski wrote:
>
> > Is there an umbrella Jira with open subtasks for every Api th
> But a little more effort on those json files that make up V2
I looked into that and during the in-depth testing realised that V2
did not support default values (it writes out current values only),
nor did it have a proper round-trip story, especially for the nested
configurations. So, it was - ar
These may be interesting and relevant:
*
https://solr.apache.org/guide/8_8/query-settings-in-solrconfig.html#enablelazyfieldloading
*
https://solr.apache.org/guide/8_8/defining-fields.html#optional-field-type-override-properties
(last entry "large")
Regards,
Alex.
On Thu, 3 Jun 2021 at 10:32
The worry I have is that this (and previous cloud-first) move pushes
Solr - even further - into Innovator's Dilemma situation. It is a
complicated and nuanced worry, so I would understand if nobody else
shares it. But I felt it was still worth mentioning.
The core issue is that even though Solr is
"Good enough/Recommended" for what? Serious question.
Because it may be - more than - good enough to "send files to the
server", but the post tool is also doing a lot of Solr business logic
that beginner users may not have understood yet. Like automatic
commit. Like choosing endpoint and content t
On v2 API,
I did some review a while ago, though the goal was to compare its
coverage with solrconfig.xml, rather than with V1.
My discoveries (umbrella and children) are in SOLR-14795 .
Regards,
Alex.
On Wed, 28 Apr 2021 at 12:04, Jan Høydahl wrote:
>
> Hi all,
>
> We've come a long way si
Congratulations Eric,
Regards,
Alex.
On Sat, 24 Apr 2021 at 07:14, Eric Pugh wrote:
>
> Thank you all! I’m excited about the future of Solr, and it’s potential to
> solve new use cases in search.
>
> On Apr 23, 2021, at 8:19 PM, Jan Høydahl wrote:
>
> I am pleased to announce that Eric Pu
+1
In terms of visibility, I think we should promote the Reference Guide on
the home page more heavily. Even if it were some sort of partial TOC
screenshot.
Regards,
Alex.
On Wed, 24 Mar 2021 at 04:38, Jan Høydahl
wrote:
> Hi,
>
> I'm proposing to remove the books section from the frontpage
Hello,
I was asked to draw attention and summarize the cross-road situation
with the current Solr 9 blocker issue about the "schemaless mode".
Basically, the current shameless mode is broken in two main ways, one
familiar and one that is a bit more obscure:
1) Familiar: The schemaless mode will u
This seems two different things here, based on the fact that you
already have a proposed solution:
1) You want a fix for the Solr you are running already? This may not
be an ideal solution, but if you fix the login.html in the
server/solr-webapp/webapp/partials, does it address your problem?
2) As
13 matches
Mail list logo
