Notices tagged with solr
-
@musicman I just heard of #MeiliSearch last night, so I did not do any deep diving. I know that #YaCy uses #Solr, but I do not know if it always did.
-
proof is in the pudding, as they say, but sounds like I have learned a variety of things this morning:
1. "Since Alfresco Installer was discontinued from Alfresco 5.2, this project provides a command line installer for Alfresco Community 6.1 and Alfresco Community 6.2 to be used in Docker Compose installations." -- not sure the background on this decision, but paired with the other information, seems as though I may have been mistaken about the #Alfresco community.
2. The Alfresco forums are super useful.
3. Even if you know nothing about a project, it might be worth checking their bug tracker. Of course, you need to know enough about the product to understand the bugs, which I probably didn't have when I started this project. Once I got confident enough in my understanding to post on the forum though, I was almost certainly qualified to go bug hunting at that point.
It's funny, because bug reports is where I generally start. I guess the difference here was I wasn't looking for an easy out for a support ticket. I guess when I am doing my own infrastructure work, I should keep some of those fire fighting habits.
That said, since we support Alfresco, as well as #solr, and #Tomcat, in the long term it is probably good that I spent some time beating my head against the wall with it. (we never get Alfresco tickets, but we do get Tomcat tickets)
-
below is a section of a #docker compose file. Why is it that under environment in share you have different sections such as JAVA_OPTS, but under solr6 the configs just have a - in front of them. I tried adding JAVA_OPTS to solr6 and got a yml syntax error
```
share:
image: alfresco/alfresco-share:6.2.0
mem_limit: 1g
environment:
REPO_HOST: "alfresco"
REPO_PORT: "8080"
JAVA_OPTS: "
-Xms500m
-Xmx500m
-Dalfresco.host=localhost
-Dalfresco.port=8080
-Dalfresco.context=alfresco
-Dalfresco.protocol=http
"
solr6:
image: alfresco/alfresco-search-services:1.4.2.1
mem_limit: 4g
environment:
#JAVA_OPTS: "-Dsolr.log.level=FINE"
#Solr needs to know how to register itself with Alfresco
- SOLR_ALFRESCO_HOST=alfresco
- SOLR_ALFRESCO_PORT=8080
#Alfresco needs to know how to call solr
- SOLR_SOLR_HOST=solr6
- SOLR_SOLR_PORT=8983
#Create the default alfresco and archive cores
- SOLR_CREATE_ALFRESCO_DEFAULTS=alfresco,archive
#HTTP by default
- ALFRESCO_SECURE_COMMS=none
```
-
On search: I really want to host another #YaCy node, but YaCy's results are still not great. Even when my node was crawling & indexing sites in a particular field (at the time, FOSS SQL and NOSQL databases) weekly, searches for things in that field were infested with non-related results such that finding the desired answer was unreliable.
.
YaCy integrates #Solr ... so its results should be improvable.
-
@musicman I only indirectly encountered #Solr when I ran a #YaCy instance, so I have no opinion about Solr 6.
-
How do people feel about #Solr 6? That's what #Alfresco uses. Latest Solr is 8.5.2
-
@musicman Good. I think the current implementation of the #YaCy search engine relies on #Solr.