I think you are confusing JWK with the JWT token. JWK is only for defining the
key, see https://mkjwk.org for an online JWK generator, you can choose HS256 as
algorithm. Put the generated JWK in Solr's config and also use the generated
key to sign your JWT. Then Solr should be able to validate t
Hi,
we changed our int fields from TrieIntField to IntPointField when we
upgraded from Solr 7.7 to 8.1.1.
We're using the termfreq function to order results and this worked with
Solr 7.7 and TrieIntField but does not work with IntPointField and Solr
8.1.1 anymore.
The field is defined as
Hi,
4 to 5 million documents.
For an NTR index, we need a field to be updated very frequently and filter
results based on it. Will In-Place updates help us?
Thanks,
Doss.
It's worth to try. I know about folks who build NRT system on it. One
thing, I might be wrong but, "pint" might mean points which is hardly
compatible with inPlace update. It should be the simplest numbers, if you
can debug Solr, check that it creates NumericDocValues, not sorted ones.
These are up
On 9/10/2019 7:15 AM, Doss wrote:
4 to 5 million documents.
For an NTR index, we need a field to be updated very frequently and filter
results based on it. Will In-Place updates help us?
Although you CAN search on docValues-only fields, the performance is
terrible. So the answer I have for
If you are interested, Apache Comdev team added Lucene and Solr items to
RedBubble:
Lucene:
https://www.redbubble.com/people/comdev/works/40953165-apache-lucene?asc=u
Solr:
https://www.redbubble.com/people/comdev/works/40952682-apache-solr?asc=u
Jan using https://mkjwk.org/
I generated the following JWK
{
"kty": "oct",
"use": "sig",
"kid": "solr",
"k":
"pIpVnjhuAj9DBg8e2lwya7o_uZMM3Wqo2eK0uchOza0vBS-orZNYTkLcHTLXF9JaCBR08tWfFEWVPENF6sXKuaj8Mn65Kc3QUmS-csblVvjj69dXk2Mi-Zs2iDDM3QyyvdiyRpfxE-xKwwjhU47xs7M0Dq69I1UE5nrFkczLf9qe3b47ha
Please check the error message in solr.log on the server side and paste that
here. Could be a bug 🕷
Jan Høydahl
> 10. sep. 2019 kl. 18:51 skrev Tyrone Tse :
>
> Jan using https://mkjwk.org/
> I generated the following JWK
>
> {
>
> "kty": "oct",
> "use": "sig",
> "kid": "solr",
> "k":
>
All I could see in the solr.log was ( could it be the java version ?)
main{ExitableDirectoryReader(UninvertingDirectoryReader(Uninverting(_0(8.2.0):C1:[diagnostics={java.vendor=Oracle
Corporation, os=Mac OS X, java.version=1.8.0_60, java.vm.version=25.60-b23,
lucene.version=8.2.0, os.arch=x86_64,
Hi,
Thanks for all this information. I am doing this now like following:
@Override
public void inform(SolrCore core) {
HttpSolrClient.Builder builder = new HttpSolrClient.Builder();
String baseURL =
core.getCoreContainer().getZkController().getBaseUrl() + "/" +
dataInfo.dataSource;
bu
Hi All,
I am using solr-5.5.5, in which I have one master and two slaves. I see some
red and some green replication iteration on my slave side.
What does these red and green iteration means?
Will this cause problem?
Thanks & Regards,
Akreeti Agarwal
::DISCLAIMER::
__
Hi there,
I was hoping that you may be able to assist us with a search issue we're facing.
Each one of these queries work on their own:
articledate:[2018-09-04T00:00:00Z TO 2019-09-10T23:59:59Z]
{!join to=id from=url}articledate:[2018-09-04T12:00:00Z TO
2019-09-10T11:59:59Z])
But if we try and
It depends on the timestamps.
The red iterations are failed replications and the green are passed
replications.
If the newest timestamp is green the latest replication went well, if it is
red, it failed.
You should check the solr log on the slave if a recent replication have
failed to see the caus
13 matches
Mail list logo
