Hello Ryan,
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, eg.
"match('@subject: piler')"
Which led me to believe the MATCH string was all that was supposed to
be
I should clarify the "error: cannot connect to 127.0.0.1:9306" error
message.
This error does not occur at compile time, but only at runtime of the
latest pilerexport, and only when the -w switch is used.
On Wed, Apr 7, 2021 at 7:36 PM Ryan Blenis wrote:
> Hi Janos,
>
> Thanks, that led me to
Hi Janos,
Thanks, that led me to what is causing the issue / confusion.
The -w switch is described as "Where condition to pass to sphinx, eg.
"match('@subject: piler')"
Which led me to believe the MATCH string was all that was supposed to be
there/replaced, however a quick look at the code
Disregard that last email. Coffee is good, not re-running ./configure after
installing deps is bad. Following up shortly with more pertinent info.
Thank you.
On Wed, Apr 7, 2021 at 3:58 PM Ryan Blenis wrote:
> Hi Janos,
>
> Thanks for the response, in trying to do this (I cloned the repo,
>
Hi Janos,
Thanks for the response, in trying to do this (I cloned the repo,
./configure --localstatedir=/var --with-database=mariadb , and ran make)
and got this:
Making all in src
make[1]: Entering directory '/tmp/piler/src/piler/src'
gcc -std=c99 -O2 -fPIC -Wall -Wextra
Hello Ryan,
please apply this patch to pilerexport.c, and recompile it.
https://bitbucket.org/jsuto/piler/commits/e6607b0bf1d44562bcf2a08e3bfed94181b7b95d
It syslogs the sphinx query. Then try the following. Enter the search
query
on the gui, and record the sphinx query syslogged. Then
Hi Janos,
I have to export potentially a ton of emails and was looking to use
pilerexport versus multiple batches of GUI searches. I saw the -w flag and
thought "great, I can use this" but it doesn't seem to respond
appropriately for my test case. I have 2 emails that match the following
