search_index | Search Index provides an easy way | Search Engine library

The procedure and conventions for quoting and escaping on the command line are quite different between Unix and Windows.

On Unix, quoting and escaping is a concern of the shell itself, and Unix shells typically understand the contents of single quotes ' as totally verbatim text, while the contents of " can contain some interpolation metacharacters but spaces are still taken literally, rather than separators. The shell handles the tokenization into a set of arguments and passes those arguments to the program as an array of strings.

On Windows, quoting and escaping is the concern of the program being run¹, and not of the command interpreter cmd.exe. The command line you type will (more or less) be passed exactly as you wrote it to the program you're running -- curl in this case -- and it's left entirely up to that program to decide what symbols like " and ' might mean and where to draw the boundaries between separate arguments.

In practice, most modern CLI applications on Windows are either built using Microsoft Visual C++ or with some other software that emulates its command line parsing conventions. If curl is such a program (which is likely, since it is written in C) then unfortunately the relevant rules are quite complicated, but for your purposes here we can reduce it to a few key facts:

• The single quote character ' is taken literally. Unlike on Unix, it does not represent verbatim text.
• You can use the double quote character " to represent a sequence where spaces should be taken literally rather than used as argument separators.

Therefore in order to write a command line that is portable across both Unix and Windows, you will need to use the double quote character " and ensure that the strings you interpolate within the quotes don't contain any characters that would be interpreted as special by either set of parsing rules.

In your case, I think that would be the following as long as you can be sure that none of the variables this refers to will contain quote characters, $ characters, or anything else that a Unix shell might interpret as special inside double quotes:

After looking into this further, the feature is not currently available for document type searches. See this issue in github for more information

I figured that it was an issue with my certificate.

I needed to add some additional config param to the ELASTICSEARCH_DSL variable. Adding this solves the issue:

the problem was with the installation of elasticsearch all I was needed was to reinstall it on my pc

For anyone interested, I managed to solve this by overriding the generate_id method of the Document so that the _id used is just a plain string:

In this case, it should be calculated only once time. Postgres detects equal expressions. Generally, if you afraid about this, then you can calculate expression in subquery.

Some like:

The second and third commands in the && chain will only run after the first one has exited, meaning after the webserver has been stopped. You'll have to add another service just for this task.

You can generate AND egrep result on-the-fly, rather than constructing command and using eval at the end.

Try replacing line 33-50 in your script with the following. See if it would work with your server.

Rather than printing each search_index inside the loop, collect all the results in a single object. Something like: