Digy,

Some additional information from the discussion on the lucene-net-user list 
with Floyd Wu.


I ran some further tests using Java Lucene 2.3.2 and JDK 1.5.

The Java equivalents of the two small test applications I use to inspect an 
index and compact it, function identically to the .NET versions (that were 
built with VS2005 and Lucene.NET 2.3.1).

That Luke cannot open the index appears to be a problem within Luke.
Even if Floyd's index contains some odd entries, Java Lucene 2.3.2 does not 
flag the index as corrupt; and both the Java and .NET versions report the same 
index content before and after the optimize operation.


-- Neal

**************************************************************
Neal Granroth
Software Engineer, Molecular Spectroscopy
Thermo Fisher Scientific
5225 Verona Road, Madison, WI 53711

neal.granr...@thermofisher.com
Tel: 608-276-5645
Fax: 608-276-6328

www.thermofisher.com

WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of this 
e-mail or the information herein by anyone other than the intended recipient, 
or an employee or agent of a system responsible for delivering the message to 
the intended recipient, is prohibited. If you are not the intended recipient, 
please inform the sender and delete all copies.

-----Original Message-----
From: Digy (JIRA) [mailto:j...@apache.org]
Sent: Wednesday, April 08, 2009 6:28 PM
To: lucene-net-dev@incubator.apache.org
Subject: [jira] Commented: (LUCENENET-169) Changes to make Lucene.NET 
compatible with ASP.NET Medium Trust Level, in hosting environments (like 
GoDaddy...)


    [ 
https://issues.apache.org/jira/browse/LUCENENET-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697335#action_12697335
 ]

Digy commented on LUCENENET-169:
--------------------------------

Although you can overcome all of them somehow;

* controlling the the lifetime of IndexWriter/IndexReader in a naturally manner,
* reopening the IndexReader only when needed using (for ex) FileSystemWatcher,
* providing a separation between data & bussiness layer,
* providing other apps an interface that may want to write its own user 
interface,
* accessing a single search service from different web apps/from load balanced 
web servers
* controlling the lifetime of searching/indexing code (without being effected 
by the restart of the IIS processes automatically when some memory limit is 
exceeded (for ex.) )
* Ability to access some system resources that can be restricted by IIS
etc.
make me think a separete search service is a better idea.But at last, it is a 
design decision of you.
(Think, A WebApp+Solr in Java world)


DIGY

> Changes to make Lucene.NET compatible with ASP.NET  Medium Trust Level, in 
> hosting environments (like GoDaddy...)
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENENET-169
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-169
>             Project: Lucene.Net
>          Issue Type: Improvement
>         Environment: ASP.NET
>            Reporter: Corey Trager
>         Attachments: FSDirectory.patch
>
>
> Microsoft has a configuration file for shared hosting for what they call 
> "Medium Trust".   There are a couple places in FSDirectory.cs  that violate 
> the restrictions of Medium Trust, but I coded workarounds, shown below.
> #1)
> // Corey Trager, Oct 2008: Commented call to GetTempPath to workaround 
> permission restrictions at shared host.
> // LOCK_DIR isn't used anyway.
> public static readonly System.String LOCK_DIR = null; // 
> SupportClass.AppSettings.Get("Lucene.Net.lockDir", 
> System.IO.Path.GetTempPath());
> #2)
>               /// <summary>Returns an array of strings, one for each Lucene 
> index file in the directory. </summary>
>               public override System.String[] List()
>               {
> /* Changes by Corey Trager, Oct 2008, to workaround permission restrictions 
> at shared host */
>                System.IO.DirectoryInfo dir = new 
> System.IO.DirectoryInfo(directory.FullName);
>               System.IO.FileInfo[] files = dir.GetFiles();
>                 string[] list = new string[files.Length];
>                 for (int i = 0; i < files.Length; i++)
>                 {
>                     list[i] = files[i].Name;
>                 }
>                 return list;
> /* end of changes */
> //            System.String[] files = 
> SupportClass.FileSupport.GetLuceneIndexFiles(directory.FullName, 
> IndexFileNameFilter.GetFilter());
> //            for (int i = 0; i < files.Length; i++)
> //            {
> //                System.IO.FileInfo fi = new System.IO.FileInfo(files[i]);
> //                files[i] = fi.Name;
> //            }
> //                      return files;
>               }

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to