Portal Engine Questions on portal engine and web parts.
Version 5.x > Portal Engine > Lucene upgrade View modes: 
User avatar
Member
Member
Jevgenij.Nekrasov-expertasa - 4/14/2010 2:46:01 AM
   
Lucene upgrade
Hello,

We are trying to upgrade Lucene.NET engine, we are trying to create custom webpart, maybe you could suggest the easiest way to do it? we want that after the new version upgrade our traits remained in force.

Br,
Jevgenij

User avatar
Kentico Developer
Kentico Developer
kentico_martind - 4/15/2010 7:27:12 AM
   
RE:Lucene upgrade
Hello Jevgenij,

Regrettably it's not possible to upgrade built-in Lucene.NET engine without source code, but we are planning to upgrade built-in Lucene.NET engine in one of future versions.

Best Regards,

Martin Dobsicek

User avatar
Member
Member
Jevgenij.Nekrasov-expertasa - 4/15/2010 9:54:31 AM
   
RE:Lucene upgrade
Hi Martin,

We have the source code of Kentico :), but still it is no sense to change it, because next time when we update Kentico we will lost all the changes we've made before, I understand correctly? Is it possible to develop some custom search adapter, which will use the newest version of Lucene or is it too complicated?

Now we've developed some custom web part and it uses new version of Lucene, but even more, when we are trying to use Kentico's BasicRepeater class to bind the result of our search,we receive some kind of exception:

[CMSAbstractTransformation.DataBind]: Cannot parse '+(*any_word) +_culture:([fi-fi TO fi-fi] [invariantifieldivaluei TO invariantifieldivaluei])': '*' or '?' not allowed as first character in WildcardQuery

but new version Lucene's parser process this search text (*any_word) correctly :(

User avatar
Kentico Developer
Kentico Developer
kentico_martind - 4/27/2010 2:51:32 AM
   
RE:Lucene upgrade
Hi Jevgenij,

Well the Lucene is changed very frequently and there are always some changes made that needs to be reflected in adapter, so it's quite complicated task to keep it updated.

But I think the '*' wildcard is supported in the built-in version already, but you need to enable leading wildcard using following Lucene setting:

QueryParser.setAllowLeadingWildcard(true)

Could you please optionally try this?

Best Regards,

Martin Dobsicek

User avatar
Member
Member
Jevgenij.Nekrasov-expertasa - 5/4/2010 6:20:18 AM
   
RE:Lucene upgrade
Hi,

Yes, of course we try this as the first solution of our problem :) but it doesn't work :(

Br,
Jevgenij

User avatar
Kentico Developer
Kentico Developer
kentico_martind - 5/18/2010 6:10:28 AM
   
RE:Lucene upgrade
Hi Jevgenij,

This issue seems to be related to highlighter. We will try to fix it in nearest version. In a meantime, could you please try to disable highlighter (remove it from transformation)?

Best Regards,

Martin Dobsicek