couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hahn <m...@hahnca.com>
Subject Re: noob problem getting started with lucene
Date Sat, 21 Jul 2012 20:58:05 GMT
> Anything in couch.log or couchdb-lucene.log?

Here are the two versions of the commands, results, and logs ...

command 1 ...
    curl http://root:xxx@localhost
:5984/_fti/local/_design/aaa/name?q=The+Buddy+Group
result ...
    {"reason":"bad_request","code":400}
couch log ...
    [Sat, 21 Jul 2012 20:40:44 GMT] [info] [<0.350.0>] 127.0.0.1 - - GET
/_fti/local/_design/aaa/name?q=The+Buddy+Group 400
Lucene log was empty

command 2 ...
     curl http://root:xxx@localhost
:5984/ri/_fti/_design/aaa/name?q=The+Buddy+Group
result ...
    {"error":"not_found","reason":"missing"}
couch log ...
   [Sat, 21 Jul 2012 20:43:20 GMT] [info] [<0.412.0>] 127.0.0.1 - - GET
/ri/_fti/_design/aaa/name?q=The+Buddy+Group 404
Lucene log was empty

So it appears nothing is getting to lucene.

My couch local.ini ...
    [httpd_global_handlers]
    _fti = {couch_httpd_proxy, handle_proxy_req, <<"http://127.0.0.1:5985
">>}

my couchdb-lucene ini ...
    [local]
    url=http://root:xxx@localhost:5985/

couch version 1.2.0
lucene version 0.9.0-SNAPSHOT from a couple of nights ago

And once again evidence that proxy is working ...
     curl http://root:xxx@localhost:5984/_fti
    {"couchdb-lucene":"Welcome","version":"0.9.0-SNAPSHOT"}
couch log ...
    [Sat, 21 Jul 2012 20:47:37 GMT] [info] [<0.126.0>] 127.0.0.1 - - GET
/_fti 200
Lucene log is empty.

The lucene log shows output when lucene is started so I have the right log
file.

On Sat, Jul 21, 2012 at 10:05 AM, Robert Newson <rnewson@apache.org> wrote:

> Hi,
>
> Anything in couch.log or couchdb-lucene.log?
>
> B.
>
> On 21 Jul 2012, at 04:54, Mark Hahn wrote:
>
> > Thanks.  That was the first URL I tried in the OP and it gave ...
> >
> >   {"reason":"bad_request","code":500}
> >
> > I guess I'll try starting over with the exact example from the readme.
>  If
> > nothing else then retyping everything may fix some typo.
> >
> > It's a shame everything has to work all at once to get anywhere.  I wish
> > there was some way to take it a step at a time and debug it.  The error
> > messages are useless.
> >
> > On Fri, Jul 20, 2012 at 4:31 PM, Robert Newson <rnewson@apache.org>
> wrote:
> >
> >> From the README:
> >>
> >> "Note: The urls via the proxy have a different form:
> >>
> >> http://127.0.0.1:5984/_fti/local/db1/_design/cl-test/idx?q=hello
> >> "
> >>
> >> Adapted to your example;
> >>
> >> curl http://root:xxx@localhost
> >> :5984/_fti/local/fi/_design/aaa/**name?q=The+Buddy+Group
> >>
> >> B.
> >>
> >> On 20 Jul 2012, at 18:15, Mark Hahn wrote:
> >>
> >>> curl http://root:xxx@localhost:5984/ri/_fti/_design/aaa/**
> >>> name?q=The+Buddy+Group
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message