What is the reason you need the matched fields? Maybe your use case can be
solved using sth completely different than knowing which fields were matched.
> Am 25.06.2022 um 06:58 schrieb Yichen Sun :
>
> Hello!
>
> I’m a MSCS student from BU and learning to use Lucene. Recently I try to
>
I think standalone would be very useful.
I propose Angular with Typescript - it fits to a more data centric approach
with data types etc.
Maybe even two types of UIs - Admin UI and a simple Search UI.
> Am 06.04.2020 um 16:53 schrieb Jan Høydahl :
>
> Thanks for kickstarting this and
Is the Kerberos authentication fixed for SSL connections in either of the
versions?
Am 08.03.2020 um 21:18 schrieb Erick Erickson :
>
> see: SOLR-14312
>
> Short form: There have been some CVEs etc. fixed since 3.5.5, but then
> 3.6.0 was released. Should we upgrade to 3.5.7 or 3.6.0? If
I think the goal „fix solr Cloud stability“ deserves some more thinking. Eg i
would start with - how to measure it - because until now it is not measured.
That means a benchmark that is close to what Solr cloud should be able to
manage should be defined, eg we want to allow up to 50,000 cores
I think it is deprecated in Solr 8.x and will disappear.
You can use Apache manifoldcf or a custom software to introduce parallelism.
> Am 07.01.2020 um 11:50 schrieb aanno.trash :
>
> Hello,
>
> I looked a bit into the code of DIH (solr dataimporthandler and
> dataimporthandler-extra). I
Is the query to Neo4j correct? Do you have all attributes in the Solr schema
defined?
I think it would be useful if you can share more information.
How is the import done? Does it work with simple queries ? How do you transform
the data for the target schem?
> Am 15.12.2019 um 19:32 schrieb
pects of the language.
> Sorry for the confusion. I'll make a point of updating the documentation to
> make sure all examples in the documentation are correct.
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
>
>> On Tue, Nov 19, 2019 at 5:56 PM Jö
d)
to return the exact results. I do not know why I did originally not include
the quotation marks around Y and N, but it seems that 8.2 accepted this and
8.3 not. I will update the Jira.
On Tue, Nov 19, 2019 at 11:25 PM Jörn Franke wrote:
> Could it be that Solr 8.3 is more strict on the if statement
Could it be that Solr 8.3 is more strict on the if statement?
the statement if(eq(1,1),Y,N)
is supposed to return the character Y (not the field). In Solr 8.2 it
returns the character Y, but in Solr 8.3 not.
On Tue, Nov 19, 2019 at 11:21 PM Jörn Franke wrote:
> thanks i will find anot
and then try running them outside of the expression as plain
> Solr queries.
>
> You can also post the Solr queries to this thread and we discuss what the
> logs say.
>
> In these cases the logs always are the way to debug whats going on.
>
>
> Joel Bernstein
> htt
Well sometimes even reindexing might not always be avoidable when upgrading.
However, there should be a more user friendly way. Not every Solr deployment
that one might inherit has foreseen this. Eg in case Solr is used as a NoSQL
database where the application puts data in Solr, but not
Well sometimes even reindexing might not always be avoidable when upgrading.
However, there should be a more user friendly way. Not every Solr deployment
that one might inherit has foreseen this. Eg in case Solr is used as a NoSQL
database where the application puts data in Solr, but not
I created a JIRA for this:
https://issues.apache.org/jira/browse/SOLR-13894
On Wed, Nov 6, 2019 at 10:45 AM Jörn Franke wrote:
> I have checked now Solr 8.3 server in admin UI. Same issue.
>
> Reproduction:
> select(search(testcollection,q=“test”,df=“Default”,defType=“edismax”,f
I guess this is also a bit normal with software that grows over the years.
One could also say that one writes the current use cases and interesting future
use cases for Solr in a document and designs from scratch new - taking only the
good pieces out of the existing software.
Of course there
I cannot say anything about the statements, but maybe it could help to
introduce Solr Improvement Proposals (SIP) similar to Kafka Improvement
Proposals (KIP) or Flink Improvement Proposals (FLIP).
I think they are helpful to facilitate design decisions and refactoring /
redesign decision.
I think it highly depends on how you want to do it. You could continue to run
4.6 and have another instance(a) with 8.2+. Then you just Index as you used to
do it until now on the new one. Once you have all the data indexed you switch
you lt application to 8.2. Of course you need to test it in
URL: https://issues.apache.org/jira/browse/SOLR-13665
>>Project: Solr
>> Issue Type: Bug
>> Security Level: Public(Default Security Level. Issues are Public)
>> Components: SolrCloud
>> Affects Versions: 8.2
>> Report
Is there something new on the release already?
thank you.
On Thu, May 23, 2019 at 6:10 PM Andrzej Białecki wrote:
> Hi all,
>
> A quick reminder that during the release process for 8.1.1 any commits to
> branch_8_1 must first be submitted as a patch in JIRA and approved by the
> release
that there are other considerations by other people.
> Am 16.05.2019 um 11:55 schrieb Ishan Chattopadhyaya
> :
>
> Does this warrant a 8.1.1 release? I think this is serious enough.
>
>> On Thu, May 16, 2019 at 12:03 PM Jörn Franke wrote:
>>
>> SOLR-13475
>&
SOLR-13475
> Am 16.05.2019 um 05:24 schrieb Ishan Chattopadhyaya
> :
>
> Please open a JIRA.
>
>> On Thu, 16 May, 2019, 8:09 AM Jörn Franke, wrote:
>> Sorry autocorrection. It is not only a admin UI issue. I described in my
>> previous email that access
Am 16.05.2019 um 04:36 schrieb Jörn Franke :
>
> Note only an admin UI issue. Access collections via their alias does not work.
>
>> Am 15.05.2019 um 15:47 schrieb Mikhail Khludnev :
>>
>> It seems creating alias in Solr Admin UI is broken. It's a minor issue for
&g
/admin/collections?action=CREATEALIAS=testalias=gettingstarted
> successfully.
> Jörn, thanks for reporting.
>
>> On Tue, May 14, 2019 at 11:03 PM Jörn Franke wrote:
>> Hi,
>>
>> I tried to upgrade from 8.0 to 8.1. I noticed that there is an issue with
>
It would be also useful to include aspects of supported/semi-supported JDKs and
versions as well as potentially OS specific issues. Finally a small sentence of
migration needs would be useful.
Some of this information is available on the web site, but I do think that it
make sense to
I guess selfwritten loader means that you split up the file in 32 kB chunks or
smaller and then posts each of those 32 kB chunks to the multi valued field.
> Am 18.01.2019 um 11:51 schrieb Kranthi Kumar K
> :
>
> Hi team,
>
> Thank you Erick Erickson ,Bernd Fehling , Jan Hoydahl for your
are different in some languages or
Boolean values.
> Am 30.12.2018 um 07:01 schrieb David Smiley :
>
> Thanks for your thoughtful response Jörn!
> ...
>> On Sat, Dec 29, 2018 at 4:14 AM Jörn Franke wrote:
>> I think it is a good idea, but I see some potential comple
I think it is a good idea, but I see some potential complexity for “deployment”
of collections. For instance, in environments where Solr is used as a shared
platform amongst several stakeholders, every time you deploy/modify a
collection you need to take care that the platform types exist. If
26 matches
Mail list logo
