No, several attempts but they all come to a halt when realizing that they
provide false sense of security due to various flaws, or too big compromise
with features and performance. So best practice is OS level.
Jan Høydahl
> 10. sep. 2021 kl. 19:47 skrev Jae Joo :
>
> The way to have an encry
The way to have an encrypted index is using OS level encryption. Is
there any other way to encrypt collection based?
Jae
With a post you don’t have to worry about single/double quotes or any other
characters like an @ or & in your query, they all go in as is from the user
input, maybe not using curl but every language has a post operation to utilize.
Kind of like placeholders for a sql query, they can contain anyt
We're also looking at Solrj to insulate us from the protocol layer entirely.
-Original Message-
From: Andy Coulson
Sent: Friday, September 10, 2021 10:37 AM
To: users@solr.apache.org
Subject: RE: qf with multiple fields in _query_ with edismax
Ahh, so yes, now I see. That is probably a
Ahh, so yes, now I see. That is probably a better approach as we actually
implement this.
-Original Message-
From: Jan Høydahl
Sent: Friday, September 10, 2021 10:12 AM
To: users@solr.apache.org
Subject: Re: qf with multiple fields in _query_ with edismax
And if you fancy looking into
I'm not sure what you mean? If you mean why use a get vs a post, I guess just
because we started with copying the url generated by the UI query console and
just kept tweaking that. I supposed we could also just use postman to
experiment using posts if that is supported.
-Original Message---
And if you fancy looking into the JSON Query DSL
(https://solr.apache.org/guide/8_9/json-query-dsl.html) then it would look
something like this
curl -X POST http://localhost:8983/solr/techproducts/query -d '
{
"query": {
"bool": {
"must": [
"name:iPod",
Do you mind if I ask why not use a post to solr?
On Fri, Sep 10, 2021 at 10:18 AM Andy Coulson
wrote:
> Thanks Erik,
>
> That did the trick! My real use case will have additional predicates - I
> merely trimmed it down to reproduce and illustrate the problem. I real
> query will probably be some
Thanks Erik,
That did the trick! My real use case will have additional predicates - I merely
trimmed it down to reproduce and illustrate the problem. I real query will
probably be something like (without encoding):
q= locale:en AND thingType:part AND _query_:"{!edismax qf='object_name
thing_na
Andy,
Use single quotes around the inner parameters, such as {!edismax
qf='object_name thing_name'}. Going even further, use the `v` parameter to
encapsulate the query string inside as well, as the parser eats everything
after the closing curly bracket otherwise. {!edismax qf='object_name
t
Hi,
I am trying to implement the standard Solr dashboard on older Grafana 4.5.2.
But, it seems that not panels are coming whenever I import it.
Is there a way to implement the dashboard?
Many thanks,
Subhajit
11 matches
Mail list logo
