[deepamehta-devel] [deepamehta3] my first test of dm3
Jörg Richter
jri at deepamehta.de
Di Nov 10 22:33:46 CET 2009
Dear Thorsten,
thanks for your valuable feedback!
Here I like to help you with your issues.
On 09.11.2009, at 13:27, Torsten Ziegler wrote:
> Dear Jörg,
>
> thanks for pushing DeepaMehta to the next step.
> The last minutes I installed the new version from github and I found
> some things that are not yet working following the Readme text.
>
> The Readme from http://github.com/jri/deepamehta3 says:
>>
>> 3.) Configure CouchDB for use with couchdb-lucene as described in
>> the README
>> <http://github.com/rnewson/couchdb-lucene/>
>>
> This page only refers to couchdb-lucene 0.5, no word about
> installation of 0.4, but I found this page:
> http://wiki.github.com/ShiftSpace/shiftspace/installation-os-x that
> helped me to go on.
Regarding the couchdb-lucene installation I've extended the README
meanwhile to make things more clear:
4. Install couchdb-lucene
** Please note:** Do not install the couchdb-lucene trunk (which is
0.5 in progress and unstable).
Instead download the latest stable version, which is 0.4, from here:
<http://cloud.github.com/downloads/rnewson/couchdb-lucene/couchdb-
lucene-0.4-jar-with-dependencies.jar.gz>
IMPORTANT: Follow this unpack instruction (the usual `gunzip` won't
work!):
<http://cloud.github.com/downloads/rnewson/couchdb-lucene/README>
5. Configure CouchDB for use with couchdb-lucene as described in the
couchdb-lucene README for version 0.4:
<http://github.com/rnewson/couchdb-lucene/tree/v0.4>
(You also get there from the project's main page
<http://github.com/rnewson/couchdb-lucene/> by choosing `v0.4` from the
`all tags` menu.)
> I am working on an ubunti 9.10 system and did put the following lines
> to the file: "/etc/couchdb/local.ini"
> these have to adjusted for your location of the couchdb-lucene
> location:
>
> [couchdb]
> os_process_timeout=60000 ; 60 seconds for couchdb-lucene
> [update_notification]
> indexer=/usr/bin/java -Dcouchdb.url=http://127.0.0.1:5984 -jar
> /data/dokumente/projekte/deepamehta/dm3/couchdb-lucene/couchdb-lucene
> -0.4-jar-with-dependencies.jar -index
> [external]
> fti=/usr/bin/java -jar
> /data/dokumente/projekte/deepamehta/dm3/couchdb-lucene/couchdb-lucene
> -0.4-jar-with-dependencies.jar -search
> [httpd_db_handlers]
> _fti={couch_httpd_external, handle_external_req, <<"fti">>}
This looks correct!
> But still the Fulltext search in dm3 brings the error message:
>
> Error while searching: {"message":"result is
> null","fileName":"http://localhost:5984/deepamehta3-db/_design/
> deepamehta3/index.html","lineNumber":23,"stack":"(\"Fulltext\")@http:/
> /localhost:5984/deepamehta3-db/_design/deepamehta3/index.html:
> 23\u000atrigger_hook(\"search\",\"Fulltext\")@
> http://localhost:5984/deepamehta3-db/_design/deepamehta3/javascript/
> deepamehta3.js:434\u000asearch([object
> Object])@http://localhost:5984/deepamehta3-db/_design/deepamehta3/
> javascript/deepamehta3.js:75\u000a([object
> Object])@http://localhost:5984/deepamehta3-db/_design/deepamehta3/
> vendor/jquery/js/jquery-1.3.2.min.js:19\u000a([object
> Event])@http://localhost:5984/deepamehta3-db/_design/deepamehta3/
> vendor/jquery/js/jquery-1.3.2.min.js:19\u000a"}
>
> while the search by time works perfectly.
Probably your couchdb process can't start the external couchdb-lucene
Java process properly.
=> Please check out:
- The user who runs your couchdb process (usually "couchdb") has
read-access to the couchdb-lucene jar file
- The user who runs your couchdb process have write-access in order to
create the Lucene index directory
- The couchdb-lucene jar file has been unpacked with "unpack200" (part
of JDK1.5) as gunzip will not work. Check the integrity of the jar file
with "unzip -t <jar file>"
=> Please try this fulltext query in your browser and tell me the
result:
http://localhost:5984/deepamehta3-db/_fti/deepamehta3/search?q=hallo*
A proper result looks like this (in the browser window):
{"q":"default:
hallo*","etag":"12391ac1c49","view_sig":"aea436d6afdba5de7244fd4cac51cc1
6","skip":0,"limit":25,"total_rows":4,"search_duration":
21,"fetch_duration":17,"rows":[{"id":"t-1173","score":
0.46587268,"fields":{"title":"Stolz
Rainer"}},{"id":"t-2646","score":0.46587268,"fields":{"title":"Hofmann
Martina"}},{"id":"t-1011","score":0.40763858,"fields":{"title":"Caroli
Nicola"}},{"id":"6381d4d1e55940d157d869646b19aec2","score":
0.038216118,"fields":{"title":"Poemspace Import"}}]}
=> What does your CouchDB log say?
If you start CouchDB in the foreground you should see the log directly.
If you run CouchDB in the background check out this files:
/var/log/couchdb/couchdb.stdout
/var/log/couchdb/couchdb.stderr
(log file locations might differ on your system)
In the log files a proper fulltext request looks like this:
[info] [<0.13745.18>] EXTERNAL: Starting process for: fti
[info] [<0.13745.18>] COMMAND: /usr/bin/java -server -jar
/Users/jri/Public/couchdb-lucene-0.4-jdk14/couchdb-lucene-0.4-jdk14.jar
-search
[info] [<0.13718.18>] 127.0.0.1 - - 'GET'
/deepamehta3-db/_fti/deepamehta3/search?q=hallo* 200
> The Readme from http://github.com/jri/deepamehta3 says in the section
> DeepaMehta 3 installation
>>
>> 2.)couchapp push --atomic http://localhost:5984/deepamehta3-db
>>
> first there is one command missing to initialize the local app
> directory "couchapp init" then the up to date couchapp does atomic
> inserts by default and does not know the --atomic option any more so
> it should read:
> couchapp push http://localhost:5984/deepamehta3-db
Regarding CouchApp installation I've extended the README meanwhile to
make things more clear:
3. Install CouchApp
** Please note:** DeepaMehta 3 has only been tested with CouchApp
versions 0.3.2 to 0.3.32 so far.
When using the newer CouchApp versions 0.3.4 or 0.4 the DeepaMehta
3 installation procedure might differ from described here.
> What I really like is that the user gets prompted before the deletion
> of nodes, as I deleted quite some data by accident in dm2
>
> Concerning the dm2 database conversion to dm3 you describe below this
> is not a major problem for me as I still dont have any "production"
> data in dm2.
>
> Thanks a lot for the work and hopefully the above points help a
> little bit.
>
> Cheers
> Torsten
I hope I could help with your issues.
Thank you again for your feedback as it helps to improve the user
experience.
Cheers
Jörg
> Jörg Richter schrieb:Dear Thorsten "Ziegi",
>>
>> a while ago you asked weather DeepaMehta 3 will be data-compatible
>> with
>> DeepaMehta 2. At that time DeepaMehta 3 existed only in planing and
>> nothing was set. Meanwhile a usable version of DeepaMehta 3 is
>> available (see http://github.com/jri)
>>
>>
>> _______________________________________________
>> deepamehta-devel mailing list
>> deepamehta-devel at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/deepamehta-devel
>>
>>
>
> <torsten.vcf>
Mehr Informationen über die Mailingliste devel