On 2021-04-08 01:36, Ryan Blenis wrote:
Thanks, that led me to what is causing the issue / confusion.
The -w switch is described as "Where condition to pass to sphinx,
Which led me to believe the MATCH string was all that was supposed
be there/replaced, however a quick look at the code shows that if
is used, it REPLACES the ENTIRE where clause. This distinction
yes, perhaps the "eg." was not that prominent in the short --help
I'll improve the docs on the website, it's lagging behind the actual
and I'll add a clarification on it.
The simplest workaround to this for others would be to note that
allows you to build your own query and negates the use of other
parameters. The ideal fix I think would be to still utilize the
parameters, but have -w content appended within the MATCH()
Such fix would only complicate things because you can define the
query using -w including the time frame, recipients, etc. Again,
add a clarification to the docs.
Aside from that: I realize I'm behind on piler (1.3.8), and would
to update to get the latest pilerexport with zip capabilities, yet
see there is no upgrade information on
https://www.mailpiler.org/wiki/current:upgrade . What is the
to the latest (1.3.11)?
Well, simply compile the new stuff, and overwrite the binaries and
GUI files. The database schema hasn't changed from 1.3.8 to 1.3.11.
However, don't rush with that. The zip export feature has a poor
performance that needs a rework.
I'd also like to add a "--num-only" type flag to pilerexport to
the number of matches before exporting (would probably imply
We have something similar. When specifying -d (or --dry-run) it
the matching serial ids, eg.
$ pilerexport -d -w "MATCH(' some query')"
I'll improve it to add "total:7" as the last line of the output, if
When trying to just compile the latest, I get the error "error:
connect to 127.0.0.1:9306  " so I'm not sure if that's an
because not all the components are upgraded, or if I had a
configure flag/path configured during the original install.
The export utility assumes searchd is listening on 127.0.0.1:9306
That part didn't change from 1.3.8 to 1.3.11.