You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Chris Armour (JIRA)" <ji...@apache.org> on 2010/03/01 18:49:07 UTC
[jira] Created: (LUCENENET-346) If Lucene.Net is used under ASP.NET
with impersonation enabled, accessing directory at location requiring this
impersonation will fail.
If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
---------------------------------------------------------------------------------------------------------------------------------------
Key: LUCENENET-346
URL: https://issues.apache.org/jira/browse/LUCENENET-346
Project: Lucene.Net
Issue Type: Bug
Environment: Windows XP, Windows Server 2003, IIS
Reporter: Chris Armour
Priority: Minor
Upon closing an index writer, Merge can be called spawning another thread. This new thread doesn't have any knowledge of current ASP.NET impersonation.
This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in constructor of MergeThread (or possibly ThreadClass) if impersonation is active and making this WindowsIdentity available to the new thread itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: Balanced Segment Mergepolicy
Posted by Hans Merkl <hm...@hmerkl.com>.
As a follow up to Ranga's request for a zipped version of 2.9.1 I would like to suggest that the link to the stable zipped release on the project page http://lucene.apache.org/lucene.net/ is updated more often. Right now, it points to a version from March 2007.
I am pretty new to Lucene.Net and when I looked at the download link, I thought that the project hasn't been worked on since 2007 and was not maintained anymore. I am glad I poked around the Subversion tree and found newer releases there. I wonder how many people look at the outdated download link, assume the project is abandoned as I did initially, and don't try it. It’s also not 100% clear which version in the Subversion is most up-to-date and stable.
Hans
-----Original Message-----
From: Ranga [mailto:ranga@capdigisoft.com]
Sent: Monday, March 01, 2010 1:13 PM
To: lucene-net-dev@lucene.apache.org
Subject: Balanced Segment Mergepolicy
Hi,
I m using Lucene.Net version 2.9.1 for my development. I m facing performance issue while updating large index. I read that zoie have contributed BalancedSegmentMergePolicy and it is available in Lucene Java 3.0 version. Since I m not aware of Java can anyone incorporate this merge policy in Lucene.Net 2.9.1/.2 as a patch. Otherwise can u guide me to handle this issue.
Also I would like to have the zipped version of Lucene.Net 2.9.1 / .2. Can anyone send me the link.
Thanks in advance
-RANGA
Balanced Segment Mergepolicy
Posted by Ranga <ra...@capdigisoft.com>.
Hi,
I m using Lucene.Net version 2.9.1 for my development. I m facing performance issue while updating large index. I read that zoie have contributed BalancedSegmentMergePolicy and it is available in Lucene Java 3.0 version. Since I m not aware of Java can anyone incorporate this merge policy in Lucene.Net 2.9.1/.2 as a patch. Otherwise can u guide me to handle this issue.
Also I would like to have the zipped version of Lucene.Net 2.9.1 / .2. Can anyone send me the link.
Thanks in advance
-RANGA
[jira] Commented: (LUCENENET-346) If Lucene.Net is used under
ASP.NET with impersonation enabled, accessing directory at location
requiring this impersonation will fail.
Posted by "Chris Armour (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841204#action_12841204 ]
Chris Armour commented on LUCENENET-346:
----------------------------------------
Without impersonation, under ASP.Net, it can be impossible to access files at network locations. So without adding impersonation on Lucene.Net threads, Merge etc. on an index in these circumstances will fail as Lucene.Net is not honouring the Identity of the ASP.Net applications.
> If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENENET-346
> URL: https://issues.apache.org/jira/browse/LUCENENET-346
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows XP, Windows Server 2003, IIS
> Reporter: Chris Armour
> Priority: Minor
>
> Upon closing an index writer, Merge can be called spawning another thread. This new thread doesn't have any knowledge of current ASP.NET impersonation.
> This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in constructor of MergeThread (or possibly ThreadClass) if impersonation is active and making this WindowsIdentity available to the new thread itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (LUCENENET-346) If Lucene.Net is used under ASP.NET
with impersonation enabled, accessing directory at location requiring this
impersonation will fail.
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Digy closed LUCENENET-346.
--------------------------
Resolution: Won't Fix
> If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENENET-346
> URL: https://issues.apache.org/jira/browse/LUCENENET-346
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows XP, Windows Server 2003, IIS
> Reporter: Chris Armour
> Priority: Minor
>
> Upon closing an index writer, Merge can be called spawning another thread. This new thread doesn't have any knowledge of current ASP.NET impersonation.
> This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in constructor of MergeThread (or possibly ThreadClass) if impersonation is active and making this WindowsIdentity available to the new thread itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-346) If Lucene.Net is used under
ASP.NET with impersonation enabled, accessing directory at location
requiring this impersonation will fail.
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840799#action_12840799 ]
Digy commented on LUCENENET-346:
--------------------------------
I don't think that making updates on an index with different users' Identity(or security context) is a good solution.
A windows service or a webservice without impersonation for index update would work well.
DIGY
> If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENENET-346
> URL: https://issues.apache.org/jira/browse/LUCENENET-346
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows XP, Windows Server 2003, IIS
> Reporter: Chris Armour
> Priority: Minor
>
> Upon closing an index writer, Merge can be called spawning another thread. This new thread doesn't have any knowledge of current ASP.NET impersonation.
> This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in constructor of MergeThread (or possibly ThreadClass) if impersonation is active and making this WindowsIdentity available to the new thread itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-346) If Lucene.Net is used under
ASP.NET with impersonation enabled, accessing directory at location
requiring this impersonation will fail.
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841369#action_12841369 ]
Digy commented on LUCENENET-346:
--------------------------------
Your ASP.Net app. (or its pool) can run under a (dummy) domain user identity which has *only* the necessary rights.
bq. Lucene.Net is not honouring the Identity of the ASP.Net applications.
This is not directly Lucene.Net's problem, since any other code trying the access a network location would also fail.
DIGY
> If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENENET-346
> URL: https://issues.apache.org/jira/browse/LUCENENET-346
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows XP, Windows Server 2003, IIS
> Reporter: Chris Armour
> Priority: Minor
>
> Upon closing an index writer, Merge can be called spawning another thread. This new thread doesn't have any knowledge of current ASP.NET impersonation.
> This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in constructor of MergeThread (or possibly ThreadClass) if impersonation is active and making this WindowsIdentity available to the new thread itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-346) If Lucene.Net is used under
ASP.NET with impersonation enabled, accessing directory at location
requiring this impersonation will fail.
Posted by "Chris Armour (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849134#action_12849134 ]
Chris Armour commented on LUCENENET-346:
----------------------------------------
Yeah, no objections. Modifying identity of AppPool is a cleaner solution.
> If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENENET-346
> URL: https://issues.apache.org/jira/browse/LUCENENET-346
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows XP, Windows Server 2003, IIS
> Reporter: Chris Armour
> Priority: Minor
>
> Upon closing an index writer, Merge can be called spawning another thread. This new thread doesn't have any knowledge of current ASP.NET impersonation.
> This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in constructor of MergeThread (or possibly ThreadClass) if impersonation is active and making this WindowsIdentity available to the new thread itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (LUCENENET-346) If Lucene.Net is used under
ASP.NET with impersonation enabled, accessing directory at location
requiring this impersonation will fail.
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847564#action_12847564 ]
Digy commented on LUCENENET-346:
--------------------------------
Hi Chris,
If you don't have any objections, I will close this issue.
DIGY
> If Lucene.Net is used under ASP.NET with impersonation enabled, accessing directory at location requiring this impersonation will fail.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENENET-346
> URL: https://issues.apache.org/jira/browse/LUCENENET-346
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows XP, Windows Server 2003, IIS
> Reporter: Chris Armour
> Priority: Minor
>
> Upon closing an index writer, Merge can be called spawning another thread. This new thread doesn't have any knowledge of current ASP.NET impersonation.
> This is easily resolved by retrieving an System.Security.Principal.WindowsIdentity in constructor of MergeThread (or possibly ThreadClass) if impersonation is active and making this WindowsIdentity available to the new thread itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.