[Dovecot] clucene build warnings?
Hi all/Timo,
Is clucene still the best/recommended method for enabling full text search?
Although I haven't enabled FTS yet, I plan on doing sometime in the future, and was going to be using clucene, but before I do, I'd like to see if I need to worry about an issue I've been seeing ever since I first installed clucene (and still get every time it is upgraded)...
I run gentoo linux on an amd64 server, and have always gotten this warning whenever it is updated (and also got it when I first installed it):
QA Notice: Package triggers severe warnings which indicate that it may exhibit random runtime failures. /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r4/work/clucene-core-2.3.3.4/src/core/CLucene/index/DocumentsWriter.cpp:129:33: warning: passing NULL to non-pointer argument 2 of ‘void* memset(void*, int, size_t)’ Please do not file a Gentoo bug and instead report the above QA issues directly to the upstream developers of this software. Homepage:http://clucene.sourceforge.net/
Has anyone else ever seen similar warnings when building clucene?
Is the gentoo ebuild output correct that this is not a gentoo bug, but is in fact a problem with upstream?
If so, is it harmless? Or should I try to get upstream to fix it?
That said, being that ianap, I probably wouldn't be much help to them, so, Timo, any chance you can see if this is a problem that needs to be addressed with them?
Thanks,
--
Best regards,
Charles
On 9/16/12 4:41 PM, Charles Marcus wrote:
Same warnings here (gentoo 32bit). The gentoo package management simply checks the gcc output for warnings, and reports them to you after the build completes. As long as the warnings are not related to patches added by gentoo, the issue should go upstream. Whether it is a serious issue, that can only be decided by reviewing the code itself, which would be more appropriate for a lucene dev than a dovecot dev ;)
I suggest that you simply report the issue upstream and see what happens. If the code is harmless, they might just change it the so that gcc doesn't complain about it in the future.
-- Tom
On 2012-09-17 4:40 AM, Tom Hendrikx <tom@whyscream.net> wrote:
Thanks Tom, but I already did, a long time ago (when I first installed it):
https://sourceforge.net/tracker/?func=detail&aid=3494798&group_id=80013&atid...
Didn't hear anything for a month, and when I posted a follow-up, was told they were busy, and would take a look in the next few days, but nothing since and that was back in March...
I just posted another follow-up, so we'll see what happens.
I was mainly interested to know if anyone else sees this warning when compiling on other systems...
--
Best regards,
Charles
On 16.9.2012, at 17.41, Charles Marcus wrote:
/var/tmp/portage/dev-cpp/clucene-2.3.3.4-r4/work/clucene-core-2.3.3.4/src/core/CLucene/index/DocumentsWriter.cpp:129:33: warning: passing NULL to non-pointer argument 2 of ‘void* memset(void*, int, size_t)’
That's wrong, but it works anyway as intended.
That said, being that ianap, I probably wouldn't be much help to them, so, Timo, any chance you can see if this is a problem that needs to be addressed with them?
CLucene seems to be a pretty dead project. They've talked something about merging with Lucene++, but that hasn't happened. I've been wondering about moving to Lucene++.
On 2012-09-17 8:21 AM, Timo Sirainen <tss@iki.fi> wrote:
CLucene seems to be a pretty dead project.
Bummer...
Was my memory correct that lucene is what you currently recommend for FTS for dovecot?
They've talked something about merging with Lucene++, but that hasn't happened. I've been wondering about moving to Lucene++.
Yuck - looks like it is java based?
--
Best regards,
Charles
On 2012-09-17 8:45 AM, Timo Sirainen <tss@iki.fi> wrote:
Both CLucene and Lucene++ are C++ ports of the original Java Lucene.
Hmmm... ok, I guess I'm missing something...
Googling lucene++ leads me to this page:
http://taschenorakel.de/mathias/2012/04/18/fulltext-search-benchmarks/
which has a link to 'lucene++', which takes me to the Apache Lucene/Solr page:
and on that page it says (among other things):
"/Lucene Core <http://lucene.apache.org/core/>/, our flagship sub-project, provides Java-based indexing and search technology, as well as spellchecking, hit highlighting and advanced analysis/tokenization capabilities."
Which seems to say that it is java based...?
--
Best regards,
Charles
Ok, just to wrap up this thread for anyone who cares, I just got a reply from the clucene dev (in response to my asking him about the possible merger of clucene and lucene++) after he said he had fixed this bug and the next version would contain the fix:
"More or less it's true. About a year ago we started to make Lucene++ to the new CLucene version, as Lucene++ (also written in C++) is a port of a newer Apache Lucene version (written in Java) as the one CLucene is a port of. But we did not want to simply merge them, but to adapt Lucene++ to the "design principles" of CLucene. E.g., Lucene++ makes heavy use of shared pointers. And in CLucene we wanted to reduce this usage in favor of performance. But this not finished and I cannot say when it will finished. Nevertheless, the new version of CLucene (if any) will be also C++ and not Java. Best regards, Veit"
On 2012-09-17 9:40 AM, Charles Marcus <CMarcus@Media-Brokers.com> wrote:
--
Best regards,
Charles Marcus I.T. Director Media Brokers International, Inc. 678.514.6200 x224 | 678.514.6299 fax
On 17.9.2012, at 16.40, Charles Marcus wrote:
This is the only page I'm aware of for the project: https://github.com/luceneplusplus/LucenePlusPlus
On 2012-09-17 10:44 AM, Timo Sirainen <tss@iki.fi> wrote:
This is the only page I'm aware of for the project: https://github.com/luceneplusplus/LucenePlusPlus
Weird... wonder which is which, or if they are one and the same...
Not much activity on that one either (most things are over a year old)...
Timo, do you foresee any issues using clucene, now or the foreseeable future (year or more)?
--
Best regards,
Charles
participants (3)
-
Charles Marcus
-
Timo Sirainen
-
Tom Hendrikx