Oh lol. How could I miss that! This is actually true for any bash command.
Glad that it worked.
On Wed, 18 Dec, 2019, 00:29 rhys J, wrote:
> On Mon, Dec 16, 2019 at 11:58 PM Paras Lehana
> wrote:
>
> > Hi Rhys,
> >
> > I use CDATA for XMLs:
> >
> >
> >
> >
> > There should be a similar
Hello All,
We recently upgraded from Solr 6.6 to Solr 7.7.2 and recently had spikes in
memory that eventually caused either an OOM or almost 100% utilization of
the available memory. After trying a few things, increasing the JVM heap,
making sure docValues were set for all Sort, facet fields
Hi!
I am trying to add a cluster policy to a freshly built 8.3.0 cluster (no
collection added). I got this error when adding such a cluster policy
{
"set-cluster-policy":[{"cores":"<3","nodeset":{"sysprop.rex.node.type":"tlog"}}]}
Basically I want to limit the number of cores for certain
On Mon, Dec 16, 2019 at 11:58 PM Paras Lehana
wrote:
> Hi Rhys,
>
> I use CDATA for XMLs:
>
>
>
>
> There should be a similar solution for JSON though I couldn't find the
> specific one on the internet. If you are okay to use XMLs for indexing, you
> can use this.
>
>
We are set on using
: Is there a way to construct a query that needs two different parsers?
: Example:
: q={!xmlparser}Hello
: AND
: q={!edismax}text_en:"foo bar"~4
The easies way to do what you're asking about would be to choose one of
those queries for "storking" purposes, and put the other one in an "fq"
: Is there a way to use combine paging's cursor feature with graph query
: parser?
it should work just fie -- the cursorMark logic doesn't care what query
parser you use.
Is there a particular problem you are running into when you send requests
using both?
-Hoss
http://www.lucidworks.com/
Hey Jan,
Is this a case of something that'd be fixed by
https://issues.apache.org/jira/browse/SOLR-13071 ?
Just wondering
Best,
Jason
On Thu, Dec 12, 2019 at 5:43 PM Jan Høydahl wrote:
>
> Try something like this
> https://gist.github.com/b330e1bea7842bcdc1e5fa3940b4a4f7
>
