[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064015#comment-13064015 ] Karl Wright commented on CONNECTORS-221: I applied the java patch but not the build patch. This is because I added code that transfers the jars to the dist/lib area into connectors/cmis/build.xml a while back. So the build patch is both unnecessary and violates the rule that the connector build.xml provides the jars necessary for the connector to run, rather than adding such logic into the root build file. The root build file's logic remains simple: just pick up what is in connectors/cmis/dist/lib, and use that. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221-branch-build-patch-2.txt, CONNECTORS-221-branch-java-patch-2.txt, CONNECTORS-221-branch-java-patch.txt, CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, screenshot-8.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13063247#comment-13063247 ] Karl Wright edited comment on CONNECTORS-221 at 7/11/11 9:46 AM: - I think your plan is fine - but let's continue to work within the same ticket. I know the attachments are getting messy, but I am planning to merge the whole connector onto trunk when it is ready, so people will not need to rely on the patches in the ticket. So please, attach both new patches to CONNECTORS-221. was (Author: kwri...@metacarta.com): I think your plan is fine - but let's continue to work within the same ticket. I know the attachments are getting messy, but I am planning to merge the whole connector onto trunk when it is ready, so people will not need to rely on the patches in the ticket. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221-branch-java-patch.txt, CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, screenshot-8.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-219) Maven pom's need to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062833#comment-13062833 ] Karl Wright commented on CONNECTORS-219: Great, I'll commit the patch(es) now. Maven pom's need to be updated -- Key: CONNECTORS-219 URL: https://issues.apache.org/jira/browse/CONNECTORS-219 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor Attachments: CONNECTORS-219.patch, CONNECTORS-219_UPDATE_HSQLDB.patch The maven poms, although not supported officially, need to be updated so that (a) they have the right ManifoldCF version numbers, and (b) include the right versions of all dependent jars. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-219) Maven pom's need to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-219: --- Resolution: Fixed Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright Status: Resolved (was: Patch Available) r1144989. Maven pom's need to be updated -- Key: CONNECTORS-219 URL: https://issues.apache.org/jira/browse/CONNECTORS-219 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 Attachments: CONNECTORS-219.patch, CONNECTORS-219_UPDATE_HSQLDB.patch The maven poms, although not supported officially, need to be updated so that (a) they have the right ManifoldCF version numbers, and (b) include the right versions of all dependent jars. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062835#comment-13062835 ] Karl Wright commented on CONNECTORS-221: I've merged the latest patch into the branch. The ACE form, however, will need to use the same conventions as all other repository connectors - so instead of relying on Solr knowing the form of the permission tokens, you'll need to convert these to opaque strings and write an authority connector that can map a user name to a set of access tokens. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221-branch-java-patch.txt, CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, screenshot-5.jpg, screenshot-6.jpg, screenshot-7.jpg, screenshot-8.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-220) Database errors cause all worker threads (and the corresponding stuffer thread) to wait indefinitely
[ https://issues.apache.org/jira/browse/CONNECTORS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-220. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright r1144356 Database errors cause all worker threads (and the corresponding stuffer thread) to wait indefinitely Key: CONNECTORS-220 URL: https://issues.apache.org/jira/browse/CONNECTORS-220 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 When ManifoldCF gets a database error from a thread, it tries to recover by resetting all threads to a known state. Unfortunately this code seems to fail, and you wind up with a frozen crawl with all worker threads in the following state: Worker thread '36' daemon prio=6 tid=0x077ed000 nid=0xa98 in Object.wait() [0x0b1af000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at org.apache.manifoldcf.crawler.system.ResetManager.waitForReset(ResetManager.java:107) - locked 0xe0005528 (a org.apache.manifoldcf.crawler.system.WorkerResetManager) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:110) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061160#comment-13061160 ] Karl Wright commented on CONNECTORS-221: Can you confirm that the patches are correct? All I see in them are: (a) a set of jars, and (b) build.xml files, no java sources at all. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061191#comment-13061191 ] Karl Wright commented on CONNECTORS-221: At first glance, this looks promising. Basic code structure seems correct. FYI, the places where I see difficulties are: (a) ACLs. I notice these are commented out. What is the design and do you need an authority too? (b) Jar dependencies. There's one that may conflict with a jar already in the standard build - saaj. I'll have to confirm that your version of saaj doesn't break the connectors that depend on the older version. (c) Formatting. The Apache standard is indent size of 2 spaces, with no tabs. If you are using Eclipse, reformatting accordingly should not be difficult for you. Other than that, thanks again! I'm thinking that I'll create a branch for doing the merge work - will let you know. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061236#comment-13061236 ] Karl Wright commented on CONNECTORS-221: Great! I've set up the branch; it's https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-221. Feel free to check it out; I'll be merging in your contribution and updating it off and on throughout the day today. If we need future patches to complete the initial integration, svn diff'ing them against the branch checkout would be the right way to go. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061245#comment-13061245 ] Karl Wright commented on CONNECTORS-221: We'll also need to include appropriate notices in LICENSE.txt and NOTICE.txt. If you can start assembling that, it would be great. Apache dependencies should be OK, but anything else needs a mention. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061259#comment-13061259 ] Karl Wright commented on CONNECTORS-221: axis-saaj.jar and saag-api.jar contain in fact the same classes. However, they are not identical. We'd probably want to continue to use the axis version since that may have special axis modifications, if it will indeed work with CMIS. However, saaj-impl.jar contains sun classes so I suspect it too is licensed by Sun/Oracle. Piergiorgio, can you describe where you got this jar? There may also be a replacement but I'm curious what the license there actually claims. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061264#comment-13061264 ] Karl Wright commented on CONNECTORS-221: I committed your patch to the branch just now, except the jars, so you should see it if you sync up. Since you're not a MCF committer, you cannot commit directly to it, but you can generate new patches against it as needed. I am planning to get the build stuff up to MCF-0.3 standards, which I will try to do shortly, but before I do even that I'm still trying to figure out how to include the jars in the appropriate way. The gene...@incubator.apache.org list will have useful recommendations about what is a legal jar to include in Apache distributions, what is not. They were the folks who pointed me at geronimo-activation.jar when I was told activation.jar was not Apache legal. I would certainly talk with the Chemistry folks, though, to find out what their understanding is and why they think it is OK to include it. And then, I'd post their answers to general@i.a.o to see if they all agree. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061311#comment-13061311 ] Karl Wright commented on CONNECTORS-221: I've resolved the legal issues, I think. The incubator says that the Sun stuff has been released under CDDL for a while and that is a permitted license, although we have to handle it properly in NOTICE.txt. That means that we should do the following: (a) Get the proper text CDDL attributions for ManifoldCF's NOTICE.txt. We can probably just take this from Chemistry's NOTICE.txt.I'd suggest adding a patch with that material if you have the time. (b) I'm going to try to replace geronimo-activation.jar with activation.jar, and also rename axis-saaj to saaj-api. I'll add saaj-impl, and all the other Chemistry jars we don't currently have, right into the main lib directory. Then we'll see what breaks. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061373#comment-13061373 ] Karl Wright commented on CONNECTORS-221: Ok - the branch now builds. I made one change - there were two stax-api jars (1.0 and 1.0.1). I kept the 1.0.1 and did not include the 1.0 version. If you can confirm that the connector works as intended when built from the branch that would be super. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061383#comment-13061383 ] Karl Wright commented on CONNECTORS-221: Included. FWIW, I don't think you sent it in the original zip, but it's there now. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-221) A CMIS connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061427#comment-13061427 ] Karl Wright commented on CONNECTORS-221: The example build patch was not correct in that it did not put the jars in the dist/jar folder for the connector. I therefore checked in a different fix. Please confirm that it works for you. A CMIS connector would be helpful - Key: CONNECTORS-221 URL: https://issues.apache.org/jira/browse/CONNECTORS-221 Project: ManifoldCF Issue Type: New Feature Components: CMIS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: CONNECTORS-221-DEPENDENCIES.txt, CONNECTORS-221-Java.txt, CONNECTORS-221-build-example-patch.txt, CONNECTORS-221.txt, CONNECTORS-221.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg Several people have asked if ManifoldCF supports CMIS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-218) LockClean should support relative path
[ https://issues.apache.org/jira/browse/CONNECTORS-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060516#comment-13060516 ] Karl Wright commented on CONNECTORS-218: This looks good - please go ahead and commit it. Don't forget to update CHANGES.txt too. LockClean should support relative path -- Key: CONNECTORS-218 URL: https://issues.apache.org/jira/browse/CONNECTORS-218 Project: ManifoldCF Issue Type: Improvement Components: API Reporter: Shinichiro Abe Priority: Minor Attachments: CONNECTORS-218.patch About a synchronization directory, LockManager supports both absolute and relative path. But LockClean supports absolute path only. Directory support of LockClean should be the same as LockManager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-217) Check running more than one of instance of agent
[ https://issues.apache.org/jira/browse/CONNECTORS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060517#comment-13060517 ] Karl Wright commented on CONNECTORS-217: Requiring AgentStop for a clean stop is actually required for multi-process deployments at this time. The how-to-build-and-deploy page is quite clear about that. So I think you are perfectly OK to insist upon it - indeed, I think it's an improvement because otherwise somebody might restart the agents process with broken locks, and your patch prevents that. Check running more than one of instance of agent Key: CONNECTORS-217 URL: https://issues.apache.org/jira/browse/CONNECTORS-217 Project: ManifoldCF Issue Type: Improvement Components: API Reporter: Shinichiro Abe Priority: Minor Attachments: CONNECTORS-217-exp.patch Now, if one runs the o.a.manifold.agents.AgentRun command twice on multi process, Java procceses run twice. Even though the case of setting sync dir, the problem occurs. In jetty the problem doesn't occur because of single process. If one runs executecommand.sh org.apache.manifold.agents.AgentRun twice, the command should warn that it is already running. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-219) Maven pom's need to be updated
Maven pom's need to be updated -- Key: CONNECTORS-219 URL: https://issues.apache.org/jira/browse/CONNECTORS-219 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core, Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor The maven poms, although not supported officially, need to be updated so that (a) they have the right ManifoldCF version numbers, and (b) include the right versions of all dependent jars. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-220) Database errors cause all worker threads (and the corresponding stuffer thread) to wait indefinitely
Database errors cause all worker threads (and the corresponding stuffer thread) to wait indefinitely Key: CONNECTORS-220 URL: https://issues.apache.org/jira/browse/CONNECTORS-220 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor When ManifoldCF gets a database error from a thread, it tries to recover by resetting all threads to a known state. Unfortunately this code seems to fail, and you wind up with a frozen crawl with all worker threads in the following state: Worker thread '36' daemon prio=6 tid=0x077ed000 nid=0xa98 in Object.wait() [0x0b1af000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at org.apache.manifoldcf.crawler.system.ResetManager.waitForReset(ResetManager.java:107) - locked 0xe0005528 (a org.apache.manifoldcf.crawler.system.WorkerResetManager) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:110) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13057495#comment-13057495 ] Karl Wright commented on CONNECTORS-214: r1141264 for mime type filtering added to the documentum connector. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13056643#comment-13056643 ] Karl Wright commented on CONNECTORS-214: r1140728 for addition of length filtering to documentum, filenet, jcifs, and file system connectors. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13056922#comment-13056922 ] Karl Wright commented on CONNECTORS-214: r1140925 for length filtering added to the remaining connectors. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-215) Setting an environment variable of agent
[ https://issues.apache.org/jira/browse/CONNECTORS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13055431#comment-13055431 ] Karl Wright commented on CONNECTORS-215: This will work fine, but may be overkill. The reason the -D switches are built using a special directory is because each connector might want to contribute some. But for -Xmx and -Xms, there can only be one such switch, so having these be built from a directory seems unnecessary. What do you think? Setting an environment variable of agent Key: CONNECTORS-215 URL: https://issues.apache.org/jira/browse/CONNECTORS-215 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process Reporter: Shinichiro Abe Priority: Minor Attachments: CONNECTORS-215-trial.patch When using ./executecommand.sh org.apache.manifoldcf.agents.AgentRun, we should have an environment variable or script parameter. (e.g. JVM heapsize of agent) We need to modify executecommand.bat too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-215) Setting an environment variable of agent
[ https://issues.apache.org/jira/browse/CONNECTORS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13055492#comment-13055492 ] Karl Wright commented on CONNECTORS-215: Having these options in a file is OK. If you look at how Tomcat works, they use an environment variable, and if the variable is not present they set it to whatever defaults are required. Either approach will do. But if you decide to use a file, then I would suggest giving it an extension (e.g. options.env) so people understand what kind of file it is. Setting an environment variable of agent Key: CONNECTORS-215 URL: https://issues.apache.org/jira/browse/CONNECTORS-215 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process Reporter: Shinichiro Abe Priority: Minor Attachments: CONNECTORS-215-trial.patch When using ./executecommand.sh org.apache.manifoldcf.agents.AgentRun, we should have an environment variable or script parameter. (e.g. JVM heapsize of agent) We need to modify executecommand.bat too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-216) Handling non-ingested documents in a repository connector needs to be made consistent and easy-to-understand
[ https://issues.apache.org/jira/browse/CONNECTORS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-216: -- Assignee: Karl Wright Handling non-ingested documents in a repository connector needs to be made consistent and easy-to-understand Key: CONNECTORS-216 URL: https://issues.apache.org/jira/browse/CONNECTORS-216 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright The way a connector writer is supposed to handle documents that should not be indexed is not clear. The IProcessActivity interface provides a method, deleteDocument(id), which removes the document from the index. But it does not record the version string when it does this, making that method only really useful for the case where the version string is empty. For cases where the version string is non-empty, you are supposed to use ingestDocument(id,version,null,null), which works fine to record the version string and allow for change detection, but is very non-obvious to the user. Suggestion is to add a new variant of deleteDocument(), which takes both an id and version, and decides automatically whether to use ingestDocument() or deleteDocument() based on the contents of the version string. Also, the old deleteDocument(id) variant should be deprecated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-216) Handling non-ingested documents in a repository connector needs to be made consistent and easy-to-understand
[ https://issues.apache.org/jira/browse/CONNECTORS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-216. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1140147. Handling non-ingested documents in a repository connector needs to be made consistent and easy-to-understand Key: CONNECTORS-216 URL: https://issues.apache.org/jira/browse/CONNECTORS-216 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 The way a connector writer is supposed to handle documents that should not be indexed is not clear. The IProcessActivity interface provides a method, deleteDocument(id), which removes the document from the index. But it does not record the version string when it does this, making that method only really useful for the case where the version string is empty. For cases where the version string is non-empty, you are supposed to use ingestDocument(id,version,null,null), which works fine to record the version string and allow for change detection, but is very non-obvious to the user. Suggestion is to add a new variant of deleteDocument(), which takes both an id and version, and decides automatically whether to use ingestDocument() or deleteDocument() based on the contents of the version string. Also, the old deleteDocument(id) variant should be deprecated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054343#comment-13054343 ] Karl Wright commented on CONNECTORS-214: The web connector already filters by mime types, but it filters using the mime types accepted by the output connection. This makes some degree of sense because presumably the output system is the determinant for what kinds of documents are acceptable for indexing. This makes me wonder whether we'd be better off adding BOTH post-fetch indexing URL filtering and mime-type filtering to the Solr output connector. Right now, the Solr output connector tells the world it accepts all mime types, but we can readily put that under user control. The downside of that approach is that some repository connectors don't even know the mime types of the documents they are crawling, and thus this feature would be superfluous and confusing with those connectors. URL filtering, though, would always be appropriate. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Erlend Garåsen Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054355#comment-13054355 ] Karl Wright commented on CONNECTORS-214: Thinking about this further. The mime-type (and length-based) filtering clearly belongs with the Solr connector in my mind. An output connector should also have a say in what URLs it will accept. Unless there are objections, I'm going to change this ticket to make it cover all three of these output filtering criteria. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Erlend Garåsen Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-214: -- Assignee: Karl Wright (was: Erlend Garåsen) Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054440#comment-13054440 ] Karl Wright commented on CONNECTORS-214: I added the necessary infrastructure in the framework for all of these related pieces in r1139294. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054473#comment-13054473 ] Karl Wright commented on CONNECTORS-214: What remains: (a) Hooking up length-based filtering in all repository connectors; (b) Hooking up URL-based filtering in at least the web and RSS connectors, and maybe the rest as well; (c) Adding filtering support in the Solr connector. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-214) Add post-extraction inclusions and exclusions into the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054581#comment-13054581 ] Karl Wright commented on CONNECTORS-214: Also, r1139390 for changes to web and RSS connectors. Add post-extraction inclusions and exclusions into the web connector Key: CONNECTORS-214 URL: https://issues.apache.org/jira/browse/CONNECTORS-214 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Erlend Garåsen Assignee: Karl Wright Fix For: ManifoldCF next If html files are excluded for a job, links in these files will not be followed. If we add inclusion and exclusion filters based on post-extraction, it will be possible to fetch only certain types of documents, such as PDFs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-212) Abort from paused state causes job to be deleted under some conditions
Abort from paused state causes job to be deleted under some conditions -- Key: CONNECTORS-212 URL: https://issues.apache.org/jira/browse/CONNECTORS-212 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Last night, I paused a file system job that was indexing into Solr. This morning, before starting Solr, I aborted the job, and waited for it to enter the End notification phase. Then, I started Solr. The job entered the Cleaning up phase, and deleted itself. Looking at the history, it appears that the notification phase had an error, which may have been the trigger for this unwelcome behavior. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-212) Abort from paused state causes job to be deleted under some conditions
[ https://issues.apache.org/jira/browse/CONNECTORS-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-212: -- Assignee: Karl Wright Abort from paused state causes job to be deleted under some conditions -- Key: CONNECTORS-212 URL: https://issues.apache.org/jira/browse/CONNECTORS-212 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Last night, I paused a file system job that was indexing into Solr. This morning, before starting Solr, I aborted the job, and waited for it to enter the End notification phase. Then, I started Solr. The job entered the Cleaning up phase, and deleted itself. Looking at the history, it appears that the notification phase had an error, which may have been the trigger for this unwelcome behavior. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-211) pack() and unpack() methods duplicated in most connectors
pack() and unpack() methods duplicated in most connectors - Key: CONNECTORS-211 URL: https://issues.apache.org/jira/browse/CONNECTORS-211 Project: ManifoldCF Issue Type: Improvement Components: Framework core Reporter: Karl Wright Priority: Minor Many connectors need the ability to pack and unpack lists and fields from strings. This functionality is currently duplicated in the connectors that need it. It would be much better if the functionality was made available in the appropriate base connector class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-211) pack() and unpack() methods duplicated in most connectors
[ https://issues.apache.org/jira/browse/CONNECTORS-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-211. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1134929. pack() and unpack() methods duplicated in most connectors - Key: CONNECTORS-211 URL: https://issues.apache.org/jira/browse/CONNECTORS-211 Project: ManifoldCF Issue Type: Improvement Components: Framework core Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 Many connectors need the ability to pack and unpack lists and fields from strings. This functionality is currently duplicated in the connectors that need it. It would be much better if the functionality was made available in the appropriate base connector class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-210) Connector instantiation code doesn't handle RuntimeException exceptions properly
[ https://issues.apache.org/jira/browse/CONNECTORS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-210: --- Component/s: Framework crawler agent Framework agents process Affects Version/s: ManifoldCF 0.3 ManifoldCF 0.1 ManifoldCF 0.2 Connector instantiation code doesn't handle RuntimeException exceptions properly Key: CONNECTORS-210 URL: https://issues.apache.org/jira/browse/CONNECTORS-210 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright When a connector, on instantiation, throws a NPE, you get the following exception thrown by the registry code: java.lang.NullPointerException cannot be cast to org.apache.manifoldcf.core.interfaces.ManifoldCFException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-210) Connector instantiation code doesn't handle RuntimeException exceptions properly
[ https://issues.apache.org/jira/browse/CONNECTORS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-210. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1133518 Connector instantiation code doesn't handle RuntimeException exceptions properly Key: CONNECTORS-210 URL: https://issues.apache.org/jira/browse/CONNECTORS-210 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 When a connector, on instantiation, throws a NPE, you get the following exception thrown by the registry code: java.lang.NullPointerException cannot be cast to org.apache.manifoldcf.core.interfaces.ManifoldCFException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-204) Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it
[ https://issues.apache.org/jira/browse/CONNECTORS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-204. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1132374. Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it Key: CONNECTORS-204 URL: https://issues.apache.org/jira/browse/CONNECTORS-204 Project: ManifoldCF Issue Type: Improvement Components: Build Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 The latest HSQLDB fixes and features make it an attractive alternative to Derby. But we need a test target that exercises it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-208) RepositoryDocument abstraction is poorly designed for metadata Readers
[ https://issues.apache.org/jira/browse/CONNECTORS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-208. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1132386 RepositoryDocument abstraction is poorly designed for metadata Readers -- Key: CONNECTORS-208 URL: https://issues.apache.org/jira/browse/CONNECTORS-208 Project: ManifoldCF Issue Type: Bug Components: Framework agents process Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 The RepositoryDocument abstraction class ostensibly allows metadata values to be Reader objects, but then fails to provide conversions between Strings and Readers and Readers and Strings. This leads to Reader metadata not being supported properly by most output connectors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-114) Derby seems too unstable in multithreaded situations to be a good database for ManifoldCF, so try to add support for HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043369#comment-13043369 ] Karl Wright commented on CONNECTORS-114: Remaining issues with HSQLDB have been resolved, so I'm closing this ticket. r1131056. Derby seems too unstable in multithreaded situations to be a good database for ManifoldCF, so try to add support for HSQLDB --- Key: CONNECTORS-114 URL: https://issues.apache.org/jira/browse/CONNECTORS-114 Project: ManifoldCF Issue Type: Bug Components: Framework core Reporter: Karl Wright Fix For: ManifoldCF 0.3 Derby seems to have multiple problems: (1) It has internal deadlocks, which even if caught cause poor performance due to stalling (CONNECTORS-111); (2) It has no support for certain SQL constructs (CONNECTORS-109 and CONNECTORS-110); (3) It locks up entirely for some people (CONNECTORS-100). HSQLDB has been recommended as another potential embedded database that might work better. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-114) Derby seems too unstable in multithreaded situations to be a good database for ManifoldCF, so try to add support for HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-114. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright I have not yet made HSQLDB the official Derby replacement, but it is currently a better embedded option for many situations than Derby is. Derby seems too unstable in multithreaded situations to be a good database for ManifoldCF, so try to add support for HSQLDB --- Key: CONNECTORS-114 URL: https://issues.apache.org/jira/browse/CONNECTORS-114 Project: ManifoldCF Issue Type: Bug Components: Framework core Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Derby seems to have multiple problems: (1) It has internal deadlocks, which even if caught cause poor performance due to stalling (CONNECTORS-111); (2) It has no support for certain SQL constructs (CONNECTORS-109 and CONNECTORS-110); (3) It locks up entirely for some people (CONNECTORS-100). HSQLDB has been recommended as another potential embedded database that might work better. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-206) HSQLDB is now a first-class ManifoldCF database; we should describe how to use it in the documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-206: --- Affects Version/s: ManifoldCF 0.3 HSQLDB is now a first-class ManifoldCF database; we should describe how to use it in the documentation -- Key: CONNECTORS-206 URL: https://issues.apache.org/jira/browse/CONNECTORS-206 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright We're currently missing pretty much all mention of HSQLDB in the documentation. This includes how to enable it: org.apache.manifoldcf.databaseimplementationclass value org.apache.manifoldcf.core.database.DBInterfaceHSQLDB ... as well as the property it has for pointing at the database instance: org.apache.manifoldcf.hsqldbdatabasepath value relative path In addition to the site documentation for how to use it, we should also consider making HSQLDB be the default example database, since it seems to have fewer real problems than Derby. But this must wait until a test suite is written for this database. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-207) ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-second retry, but should probably abort the job instead
ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-second retry, but should probably abort the job instead -- Key: CONNECTORS-207 URL: https://issues.apache.org/jira/browse/CONNECTORS-207 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3 Reporter: Karl Wright The way a worker thread treats ManifoldCFException type REPOSITORY_CONNECTION_ERROR is no longer correct. It should probably just allow the job to be aborted with no retries. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-207) ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead
[ https://issues.apache.org/jira/browse/CONNECTORS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-207: --- Description: The way a worker thread treats ManifoldCFException type REPOSITORY_CONNECTION_ERROR is to wait 5 minutes and retry. It might want to just allow the job to be aborted with no retries. The current behavior is not actually *wrong*, but the circumstances under which it was added were the result of severe problems at various sites that were unrelated to ManifoldCF. was: The way a worker thread treats ManifoldCFException type REPOSITORY_CONNECTION_ERROR is no longer correct. It should probably just allow the job to be aborted with no retries. Priority: Minor (was: Major) Summary: ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead (was: ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-second retry, but should probably abort the job instead) ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead -- Key: CONNECTORS-207 URL: https://issues.apache.org/jira/browse/CONNECTORS-207 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor The way a worker thread treats ManifoldCFException type REPOSITORY_CONNECTION_ERROR is to wait 5 minutes and retry. It might want to just allow the job to be aborted with no retries. The current behavior is not actually *wrong*, but the circumstances under which it was added were the result of severe problems at various sites that were unrelated to ManifoldCF. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-204) Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it
[ https://issues.apache.org/jira/browse/CONNECTORS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044007#comment-13044007 ] Karl Wright commented on CONNECTORS-204: r1131177 has part of the code. Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it Key: CONNECTORS-204 URL: https://issues.apache.org/jira/browse/CONNECTORS-204 Project: ManifoldCF Issue Type: Improvement Components: Build Reporter: Karl Wright Assignee: Karl Wright The latest HSQLDB fixes and features make it an attractive alternative to Derby. But we need a test target that exercises it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby
[
https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042655#comment-13042655
]
Karl Wright commented on CONNECTORS-110:
HSQLDB is now also in roughly the same situation, although I've gotten a rough
outline of a way to make this work involving temporary tables. This is as
follows:
SELECT * FROM (SELECT DISTINCT customerid FROM invoice) AS i_one,
LATERAL ( SELECT id, total FROM invoice WHERE customerid =
i_one.customerid ORDER BY total DESC LIMIT 1) AS i_two
... where invoice would be a temporary table created on the fly, as follows:
DECLARE LOCAL TEMPORARY TABLE T AS (SELECT statement) [ON COMMIT {
PRESERVE | DELETE } ROWS]
For example:
DECLARE LOCAL TEMPORARY TABLE invoice AS (SELECT * FROM whatever) ON COMMIT
DELETE ROWS WITH DATA
then perform the kind of query I suggested.
The issue is that this does not fit in a our single-query abstraction metaphor
at all. Maybe a (different but identically named) stored procedure could be
generated on all three databases that would do the trick. Alternatively, all
databases could go the temporary table route, but then PostgreSQL would be
unnecessarily crippled.
Max activity and Max bandwidth reports don't work properly under Derby
--
Key: CONNECTORS-110
URL: https://issues.apache.org/jira/browse/CONNECTORS-110
Project: ManifoldCF
Issue Type: Bug
Components: Framework crawler agent
Reporter: Karl Wright
The reason for the failure is because the queries used are doing the
Postgresql DISTINCT ON (xxx) syntax, which Derby does not support.
Unfortunately, there does not seem to be a way in Derby at present to do
anything similar to DISTINCT ON (xxx), and the queries really can't be done
without that.
One option is to introduce a getCapabilities() method into the database
implementation, which would allow ACF to query the database capabilities
before even presenting the report in the navigation menu in the UI. Another
alternative is to do a sizable chunk of resultset processing within ACF,
which would require not only the DISTINCT ON() implementation, but also the
enclosing sort and limit stuff. It's the latter that would be most
challenging, because of the difficulties with i18n etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-110: --- Summary: Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB (was: Max activity and Max bandwidth reports don't work properly under Derby) Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB Key: CONNECTORS-110 URL: https://issues.apache.org/jira/browse/CONNECTORS-110 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Reporter: Karl Wright The reason for the failure is because the queries used are doing the Postgresql DISTINCT ON (xxx) syntax, which Derby does not support. Unfortunately, there does not seem to be a way in Derby at present to do anything similar to DISTINCT ON (xxx), and the queries really can't be done without that. One option is to introduce a getCapabilities() method into the database implementation, which would allow ACF to query the database capabilities before even presenting the report in the navigation menu in the UI. Another alternative is to do a sizable chunk of resultset processing within ACF, which would require not only the DISTINCT ON() implementation, but also the enclosing sort and limit stuff. It's the latter that would be most challenging, because of the difficulties with i18n etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-204) Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it
Now that HSQLDB functions with ManifoldCF, write a test-hsqldb ant target to test it Key: CONNECTORS-204 URL: https://issues.apache.org/jira/browse/CONNECTORS-204 Project: ManifoldCF Issue Type: Improvement Components: Build Reporter: Karl Wright The latest HSQLDB fixes and features make it an attractive alternative to Derby. But we need a test target that exercises it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-203) Consider porting ManifoldCF to Java 1.5 code standards
[ https://issues.apache.org/jira/browse/CONNECTORS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042724#comment-13042724 ] Karl Wright commented on CONNECTORS-203: I've merged in all the major interface changes into trunk in r1130475. The branch can now go away and further changes be made incrementally on trunk. Consider porting ManifoldCF to Java 1.5 code standards -- Key: CONNECTORS-203 URL: https://issues.apache.org/jira/browse/CONNECTORS-203 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority, Authority Service, Build, Documentation, Documentum connector, File system connector, FileNet connector, Framework agents process, Framework core, Framework crawler agent, GTS connector, JCIFS connector, JDBC connector, LiveLink connector, Lucene/SOLR connector, Meridio connector, RSS connector, SharePoint connector, Web connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Consider porting ManifoldCF to Java 1.5 standards. This includes (but is not limited to): - build files - removing use of enum variable name - introducing generics in both implementation code and interfaces (cautiously) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-205) Database DISTINCT ON abstraction needs to include ordering information in order to work for HSQLDB
Database DISTINCT ON abstraction needs to include ordering information in order to work for HSQLDB -- Key: CONNECTORS-205 URL: https://issues.apache.org/jira/browse/CONNECTORS-205 Project: ManifoldCF Issue Type: Bug Components: Framework core, Framework crawler agent Reporter: Karl Wright The constructDistinctOnClause database method cannot support HSQLDB because it presumes that the ORDER BY clause is already part of the base query. This blocks us from using the HSQLDB WITH/LATERAL temporary table solution for the functionality. Adding ORDER BY information to the abstraction should work for all databases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042861#comment-13042861 ] Karl Wright commented on CONNECTORS-110: r1130644 implements this for HSQLDB. Unfortunately, performance is extremely slow, even when the number of rows in the temporary table is only a few dozen. Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB Key: CONNECTORS-110 URL: https://issues.apache.org/jira/browse/CONNECTORS-110 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Reporter: Karl Wright The reason for the failure is because the queries used are doing the Postgresql DISTINCT ON (xxx) syntax, which Derby does not support. Unfortunately, there does not seem to be a way in Derby at present to do anything similar to DISTINCT ON (xxx), and the queries really can't be done without that. One option is to introduce a getCapabilities() method into the database implementation, which would allow ACF to query the database capabilities before even presenting the report in the navigation menu in the UI. Another alternative is to do a sizable chunk of resultset processing within ACF, which would require not only the DISTINCT ON() implementation, but also the enclosing sort and limit stuff. It's the latter that would be most challenging, because of the difficulties with i18n etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-203) Consider porting ManifoldCF to Java 1.5 code standards
[ https://issues.apache.org/jira/browse/CONNECTORS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13041503#comment-13041503 ] Karl Wright commented on CONNECTORS-203: I've created a branch (branches/CONNECTORS-203) for this work, and have begun the changes there. If the community agrees we should do this, we can finish the generics work in the branch and commit the whole thing into trunk. Consider porting ManifoldCF to Java 1.5 code standards -- Key: CONNECTORS-203 URL: https://issues.apache.org/jira/browse/CONNECTORS-203 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority, Authority Service, Build, Documentation, Documentum connector, File system connector, FileNet connector, Framework agents process, Framework core, Framework crawler agent, GTS connector, JCIFS connector, JDBC connector, LiveLink connector, Lucene/SOLR connector, Meridio connector, RSS connector, SharePoint connector, Web connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Consider porting ManifoldCF to Java 1.5 standards. This includes (but is not limited to): - build files - removing use of enum variable name - introducing generics in both implementation code and interfaces (cautiously) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-19) Look into converting SOLR connector to use SolrJ java library
[ https://issues.apache.org/jira/browse/CONNECTORS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038521#comment-13038521 ] Karl Wright commented on CONNECTORS-19: --- That's why this ticket was created - to explore using solrj instead of the homegrown code currently in the connector. However, there are issues we need to consider before solrj would be an option. The guaranteed delivery problem is one such. But also if SolrJ spins up its own threads it might well make it difficult to shut ManifoldCF down properly, depending on how those threads are created. Just as it is better to use an application server's thread pool when you are a web application, the same principles apply for threads created by connectors and their supporting libraries. If you have access to ManifoldCF in Action, you might want to have a look at chapters 5 and 6 for details. However, that does not rule solrj out, it just means we need to be cautious if and when the Solr connector is transitioned to use it. If you want to explore this in detail by all means feel free - patches are definitely welcome. Look into converting SOLR connector to use SolrJ java library - Key: CONNECTORS-19 URL: https://issues.apache.org/jira/browse/CONNECTORS-19 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Reporter: Karl Wright Priority: Minor The SOLR connector currently uses its own multipart post code. It might be a good idea to convert it to use the SolrJ client api jar instead. This would require license confirmation, plus research to make sure there are no jar conflicts as a result, with any other connector. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038658#comment-13038658 ] Karl Wright commented on CONNECTORS-202: Yes, making it explicit is preferred. But I thought you wanted to be able to set this on a per-job basis? SOLR connector suport for commitWithin -- Key: CONNECTORS-202 URL: https://issues.apache.org/jira/browse/CONNECTORS-202 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2 Reporter: Jan Høydahl Labels: commit The output connection must support commitWithin (http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22add.22) in addition to sending a commit() at the end of a job. This allows for efficient handling of commits on the Solr side. The parameter should ideally be configurable per job. In that way you could say that for Important job commitWithin=10s while for Big crawl job, commitWithin=600s. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-201) Carrydown methods should have their own interface class
Carrydown methods should have their own interface class --- Key: CONNECTORS-201 URL: https://issues.apache.org/jira/browse/CONNECTORS-201 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor The carrydown methods are shared in IVersionActivity and IProcessActivity. They ought to have their own interface. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-201) Carrydown methods should have their own interface class
[ https://issues.apache.org/jira/browse/CONNECTORS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-201. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1126427 Carrydown methods should have their own interface class --- Key: CONNECTORS-201 URL: https://issues.apache.org/jira/browse/CONNECTORS-201 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 The carrydown methods are shared in IVersionActivity and IProcessActivity. They ought to have their own interface. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-19) Look into converting SOLR connector to use SolrJ java library
[ https://issues.apache.org/jira/browse/CONNECTORS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13038360#comment-13038360 ] Karl Wright commented on CONNECTORS-19: --- The promised patch never materialized. One point, though, is that ManifoldCF is not single-threaded in any case, so you'd be unlikely to gain much in performance by going multithread on an already multi-threaded connector implementation. The current connector can maintain and use as many connections to Solr as you tell it. Memory buffering on the client side also is not a good idea because it violates the basic ManifoldCF principle that you can safely shut down and restart ManifoldCF at any time without loss. Solr also suffers from lack of a guaranteed delivery metaphor, which I've talked to the Solr team about in the past. The Solr commit model currently does not work this way but ManifoldCF really requires it, because without it there is no way to properly implement an incremental crawler. This would mean a significant new Solr feature. Look into converting SOLR connector to use SolrJ java library - Key: CONNECTORS-19 URL: https://issues.apache.org/jira/browse/CONNECTORS-19 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Reporter: Karl Wright Priority: Minor The SOLR connector currently uses its own multipart post code. It might be a good idea to convert it to use the SolrJ client api jar instead. This would require license confirmation, plus research to make sure there are no jar conflicts as a result, with any other connector. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-200) Solr connector should treat TikaException the same as a 400 response
[ https://issues.apache.org/jira/browse/CONNECTORS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-200. Resolution: Fixed Fix Version/s: ManifoldCF 0.3 r1125333 Solr connector should treat TikaException the same as a 400 response Key: CONNECTORS-200 URL: https://issues.apache.org/jira/browse/CONNECTORS-200 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Solr connector should treat TikaException the same as a 400 response, which is to skip the document. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-200) Solr connector should treat TikaException the same as a 400 response
Solr connector should treat TikaException the same as a 400 response Key: CONNECTORS-200 URL: https://issues.apache.org/jira/browse/CONNECTORS-200 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Solr connector should treat TikaException the same as a 400 response, which is to skip the document. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-200) Solr connector should treat TikaException the same as a 400 response
[ https://issues.apache.org/jira/browse/CONNECTORS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036166#comment-13036166 ] Karl Wright commented on CONNECTORS-200: r1124712 is a trial fix. Solr connector should treat TikaException the same as a 400 response Key: CONNECTORS-200 URL: https://issues.apache.org/jira/browse/CONNECTORS-200 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Solr connector should treat TikaException the same as a 400 response, which is to skip the document. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-199) Modify site release page to include new release
Modify site release page to include new release --- Key: CONNECTORS-199 URL: https://issues.apache.org/jira/browse/CONNECTORS-199 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF next Reporter: Karl Wright The site release page needs to be modified, so that the site points to the new release (0.2-incubating). Also, the PostgreSQL caveat only applies to the 0.1-incubating release, and will not to the 0.2-incubating release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-198) The build.xml rat-source target complains about files in the test-output-postgres folders
The build.xml rat-source target complains about files in the test-output-postgres folders - Key: CONNECTORS-198 URL: https://issues.apache.org/jira/browse/CONNECTORS-198 Project: ManifoldCF Issue Type: Bug Affects Versions: ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright If you run ant rat-sources, you get complaints about files under various test-output-postgresql folders, which should be excluded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-198) The build.xml rat-source target complains about files in the test-output-postgres folders
[ https://issues.apache.org/jira/browse/CONNECTORS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-198. Resolution: Fixed Fix Version/s: ManifoldCF next r1100916. The build.xml rat-source target complains about files in the test-output-postgres folders - Key: CONNECTORS-198 URL: https://issues.apache.org/jira/browse/CONNECTORS-198 Project: ManifoldCF Issue Type: Bug Affects Versions: ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next If you run ant rat-sources, you get complaints about files under various test-output-postgresql folders, which should be excluded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.
[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030669#comment-13030669 ] Karl Wright commented on CONNECTORS-197: In the patch, the following lines look incorrect: +option value=\sAMAccountName\+(org.apache.manifoldcf.ui.util.Encoder.attributeEscape(userACLsUsername).equals(sAMAccountName)? selected=\true\:)+sAMAccountName/option\n+ +option value=\userPrincipalName\+(org.apache.manifoldcf.ui.util.Encoder.attributeEscape(userACLsUsername).equals(userPrincipalName)? selected=\true\:)+userPrincipalName/option\n+ You want to attributeEscape the value attribute, not the equals compare. Other than that, the patch looks good. Would you like to fix this and I will go ahead and commit it? Active directory authority provides a compatibility switch for getting SID. Key: CONNECTORS-197 URL: https://issues.apache.org/jira/browse/CONNECTORS-197 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-197-temp.patch, CONNECTORS-197.patch When using /UserACLs?username=foo@bar, MCF always refers to samAccountName now. Size of samAccountName is specified as less than 20 characters. Size of Login Name is specified as over 20 characters(256). if a user does not support old version of OS and support only new version, it is hard for ManifoldCF to restrict 20 characters of Login name. We want a compatibility switch in the configuration switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.
[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030670#comment-13030670 ] Karl Wright commented on CONNECTORS-197: It looks like I confused Jira on the previous comment ;-) Hopefully you will be able to figure out what I meant. Active directory authority provides a compatibility switch for getting SID. Key: CONNECTORS-197 URL: https://issues.apache.org/jira/browse/CONNECTORS-197 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-197-temp.patch, CONNECTORS-197.patch When using /UserACLs?username=foo@bar, MCF always refers to samAccountName now. Size of samAccountName is specified as less than 20 characters. Size of Login Name is specified as over 20 characters(256). if a user does not support old version of OS and support only new version, it is hard for ManifoldCF to restrict 20 characters of Login name. We want a compatibility switch in the configuration switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-174) The standard logging.ini file for the Quick Start should set a log format that includes at least date and time
[ https://issues.apache.org/jira/browse/CONNECTORS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-174: --- Resolution: Fixed Fix Version/s: ManifoldCF next Status: Resolved (was: Patch Available) r1100971. The standard logging.ini file for the Quick Start should set a log format that includes at least date and time -- Key: CONNECTORS-174 URL: https://issues.apache.org/jira/browse/CONNECTORS-174 Project: ManifoldCF Issue Type: Improvement Components: Examples Affects Versions: ManifoldCF next Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-174.patch The log format as currently set by default for the Quick Start could be better if it included a date, time, and maybe a thread ID. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.
[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-197. Resolution: Fixed Assignee: Karl Wright r1100987. Active directory authority provides a compatibility switch for getting SID. Key: CONNECTORS-197 URL: https://issues.apache.org/jira/browse/CONNECTORS-197 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Reporter: Shinichiro Abe Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-197-temp.patch, CONNECTORS-197.patch When using /UserACLs?username=foo@bar, MCF always refers to samAccountName now. Size of samAccountName is specified as less than 20 characters. Size of Login Name is specified as over 20 characters(256). if a user does not support old version of OS and support only new version, it is hard for ManifoldCF to restrict 20 characters of Login name. We want a compatibility switch in the configuration switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.
[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030711#comment-13030711 ] Karl Wright commented on CONNECTORS-197: Yes, you are correct. The only thing I changed from your second patch was to add support for backwards compatibility in case the new parameter is not there. Active directory authority provides a compatibility switch for getting SID. Key: CONNECTORS-197 URL: https://issues.apache.org/jira/browse/CONNECTORS-197 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Reporter: Shinichiro Abe Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-197-temp.patch, CONNECTORS-197.patch When using /UserACLs?username=foo@bar, MCF always refers to samAccountName now. Size of samAccountName is specified as less than 20 characters. Size of Login Name is specified as over 20 characters(256). if a user does not support old version of OS and support only new version, it is hard for ManifoldCF to restrict 20 characters of Login name. We want a compatibility switch in the configuration switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots
[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030551#comment-13030551 ] Karl Wright commented on CONNECTORS-194: Patch looks great! I'll commit it tomorrow morning. Forrest doc build always gets an error because of relative references to javadoc roots -- Key: CONNECTORS-194 URL: https://issues.apache.org/jira/browse/CONNECTORS-194 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Attachments: CONNECTORS-194.patch Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc itself is not under Forrest's control. Somebody needs to find a better way of handling this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-197) Active directory authority provides a compatibility switch for getting SID.
[ https://issues.apache.org/jira/browse/CONNECTORS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030568#comment-13030568 ] Karl Wright commented on CONNECTORS-197: You might want to have a look at the changes I committed today from Kadri. I think your patch may need to be changed to just substitute the uid attribute for the sAMAccountName attribute when the switch is set. Active directory authority provides a compatibility switch for getting SID. Key: CONNECTORS-197 URL: https://issues.apache.org/jira/browse/CONNECTORS-197 Project: ManifoldCF Issue Type: Improvement Components: Active Directory authority Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-197-temp.patch When using /UserACLs?username=foo@bar, MCF always refers to samAccountName now. Size of samAccountName is specified as less than 20 characters. Size of Login Name is specified as over 20 characters(256). if a user does not support old version of OS and support only new version, it is hard for ManifoldCF to restrict 20 characters of Login name. We want a compatibility switch in the configuration switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-196) Active directory authority doesn't work if login name and common name differ
[ https://issues.apache.org/jira/browse/CONNECTORS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-196. Resolution: Fixed Fix Version/s: ManifoldCF next r1100090 Active directory authority doesn't work if login name and common name differ Key: CONNECTORS-196 URL: https://issues.apache.org/jira/browse/CONNECTORS-196 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next Active directory authority will not work if common name (cn) and login name (sAMAccountName) differ. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-196) Active directory authority doesn't work if login name and common name differ
Active directory authority doesn't work if login name and common name differ Key: CONNECTORS-196 URL: https://issues.apache.org/jira/browse/CONNECTORS-196 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Active directory authority will not work if common name (cn) and login name (sAMAccountName) differ. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-196) Active directory authority doesn't work if login name and common name differ
[ https://issues.apache.org/jira/browse/CONNECTORS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13029779#comment-13029779 ] Karl Wright commented on CONNECTORS-196: Also, r1100097. Active directory authority doesn't work if login name and common name differ Key: CONNECTORS-196 URL: https://issues.apache.org/jira/browse/CONNECTORS-196 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next Active directory authority will not work if common name (cn) and login name (sAMAccountName) differ. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028090#comment-13028090 ] Karl Wright commented on CONNECTORS-195: The patch requires the name of an attribute that all users have. uid is what it uses now. Online references are not clear on whether or not this will always work with Active Directory. It especially does not seem to exist for Windows 2000. Another suggestion is sAMAccountName, which exists for all versions of Windows. Replacing uid in the patch with sAMAccountName may therefore make it work better. Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028091#comment-13028091 ] Karl Wright commented on CONNECTORS-195: The following reference is very helpful. http://msdn.microsoft.com/en-us/library/ms679635%28v=VS.85%29.aspx Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots
[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028282#comment-13028282 ] Karl Wright commented on CONNECTORS-194: cli-xconf seems definitely the way to go. But we're still going to need a jumping-off page that is handled by Forrest (which is what javadoc.html does for us) because not all connectors are buildable or can be javadoc'd, depending on the existence of the needed third-party libraries. If the api subdirectory is the new place where the javadoc roots are all put, that's fine by me. Forrest doc build always gets an error because of relative references to javadoc roots -- Key: CONNECTORS-194 URL: https://issues.apache.org/jira/browse/CONNECTORS-194 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc itself is not under Forrest's control. Somebody needs to find a better way of handling this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots
[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028282#comment-13028282 ] Karl Wright edited comment on CONNECTORS-194 at 5/3/11 4:08 PM: cli-xconf seems definitely the way to go. But we're still going to need a jumping-off page that is handled by Forrest (which is what javadoc.html does for us). Moving javadoc.html to api/index.html for this purpose is also OK if we can get forrest to work with it properly in that location. If the api subdirectory is the new place where the javadoc roots are all put, that's fine by me. was (Author: kwri...@metacarta.com): cli-xconf seems definitely the way to go. But we're still going to need a jumping-off page that is handled by Forrest (which is what javadoc.html does for us) because not all connectors are buildable or can be javadoc'd, depending on the existence of the needed third-party libraries. If the api subdirectory is the new place where the javadoc roots are all put, that's fine by me. Forrest doc build always gets an error because of relative references to javadoc roots -- Key: CONNECTORS-194 URL: https://issues.apache.org/jira/browse/CONNECTORS-194 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc itself is not under Forrest's control. Somebody needs to find a better way of handling this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-195: -- Assignee: Karl Wright Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-195. Resolution: Fixed Fix Version/s: ManifoldCF next Verified that the committed fix does the expected thing on a certain user's setup. Awaiting final verification that it does not break a user with a correct setup, although this would be extremely unlikely. Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-195: --- Attachment: CONNECTORS-195.patch Patch which may work to resolve the issue Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-192) Job-related specification post method sometimes called without corresponding specification header/body
Job-related specification post method sometimes called without corresponding specification header/body -- Key: CONNECTORS-192 URL: https://issues.apache.org/jira/browse/CONNECTORS-192 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright For specification tabs, sometimes the specification post method is called when the corresponding specification header/body method wasn't. This can happen for both repository and output connectors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-193) Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods
Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods - Key: CONNECTORS-193 URL: https://issues.apache.org/jira/browse/CONNECTORS-193 Project: ManifoldCF Issue Type: Bug Components: GTS connector, Lucene/SOLR connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright The convention for form elements and javascript methods is that all element names and methods must begin with lowercase oc. The convention for output specification tabs is that the tab name should contain the name of the target, e.g. GTS Parameters or Solr Metadata Mapping. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots
Forrest doc build always gets an error because of relative references to javadoc roots -- Key: CONNECTORS-194 URL: https://issues.apache.org/jira/browse/CONNECTORS-194 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc itself is not under Forrest's control. Somebody needs to find a better way of handling this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-189) Add the mail archive links to the mail.html page
[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026154#comment-13026154 ] Karl Wright commented on CONNECTORS-189: Please! What did you have in mind? (Bear in mind that there's already a Lucid Imagination search box at the top.) Add the mail archive links to the mail.html page Key: CONNECTORS-189 URL: https://issues.apache.org/jira/browse/CONNECTORS-189 Project: ManifoldCF Issue Type: Improvement Affects Versions: ManifoldCF 0.2 Reporter: Farzad Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-189.patch, mail.xml I think this would best be added to the mail.html page, which describes the mail lists and how to sign up for them. Please feel free to open a jira ticket accordingly. Thanks! Karl On Tue, Apr 26, 2011 at 11:34 AM, conflue...@apache.org wrote: Space: Apache Connectors Framework (https://cwiki.apache.org/confluence/display/CONNECTORS) Page: FAQ (https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ) Comment: https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ?focusedCommentId=26119029#comment-26119029 Comment added by Farzad: - Found the root links, this is nice. Might want to add these to the FAQ. Do you know if there is a way to view snippets of the messages without having to click on each one? http://www.mail-archive.com/connectors-user@incubator.apache.org/index.html http://www.mail-archive.com/connectors-dev@incubator.apache.org/index.html http://www.mail-archive.com/general@incubator.apache.org/index.html In reply to a comment by Karl Wright: The news lists are in fact kept around; you can in fact use google to find old posts. Try googling ManifoldCF eclipse to see what I mean. Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-191) All .bat files should have CRLF attribute in svn
All .bat files should have CRLF attribute in svn Key: CONNECTORS-191 URL: https://issues.apache.org/jira/browse/CONNECTORS-191 Project: ManifoldCF Issue Type: Bug Components: Documentum connector, FileNet connector, Framework agents process Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Priority: Minor All .bat files should have svn:eol-style CRLF in svn, so they always have cr/lf endings. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-191) All .bat files should have CRLF attribute in svn
[ https://issues.apache.org/jira/browse/CONNECTORS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-191. Resolution: Fixed Fix Version/s: ManifoldCF next r1097349 All .bat files should have CRLF attribute in svn Key: CONNECTORS-191 URL: https://issues.apache.org/jira/browse/CONNECTORS-191 Project: ManifoldCF Issue Type: Bug Components: Documentum connector, FileNet connector, Framework agents process Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF next All .bat files should have svn:eol-style CRLF in svn, so they always have cr/lf endings. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-190) Programmatic operation page has a wiki link in a Forrest page
Programmatic operation page has a wiki link in a Forrest page - Key: CONNECTORS-190 URL: https://issues.apache.org/jira/browse/CONNECTORS-190 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Priority: Minor The following wiki markup is present in the programmatic-operation.xml page: [here|http://www.json.org] This should be an a href tag instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-190) Programmatic operation page has a wiki link in a Forrest page
[ https://issues.apache.org/jira/browse/CONNECTORS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-190. Resolution: Fixed Assignee: Karl Wright r1097192. Programmatic operation page has a wiki link in a Forrest page - Key: CONNECTORS-190 URL: https://issues.apache.org/jira/browse/CONNECTORS-190 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Priority: Minor The following wiki markup is present in the programmatic-operation.xml page: [here|http://www.json.org] This should be an a href tag instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-188) CRLF line endings in executecommand.sh script
[ https://issues.apache.org/jira/browse/CONNECTORS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-188: -- Assignee: Karl Wright CRLF line endings in executecommand.sh script - Key: CONNECTORS-188 URL: https://issues.apache.org/jira/browse/CONNECTORS-188 Project: ManifoldCF Issue Type: Bug Components: Framework agents process Environment: *NIX Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.2 The executecommand.sh script cannot be run since CRLF line endings have been added: $ bash -x processes/script/executecommand.sh + $'\r' : command not foundecutecommand.sh: line 2: + $'\r' : command not foundecutecommand.sh: line 17: 'rocesses/script/executecommand.sh: line 30: syntax error near unexpected token `do 'rocesses/script/executecommand.sh: line 30: `for filename in $(ls -1 $MCF_HOME/processes/jar) ; do -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-188) CRLF line endings in executecommand.sh script
[ https://issues.apache.org/jira/browse/CONNECTORS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-188. Resolution: Fixed Fix Version/s: ManifoldCF next r1096922 (trunk) r1096925 (release branch) CRLF line endings in executecommand.sh script - Key: CONNECTORS-188 URL: https://issues.apache.org/jira/browse/CONNECTORS-188 Project: ManifoldCF Issue Type: Bug Components: Framework agents process Environment: *NIX Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.2, ManifoldCF next The executecommand.sh script cannot be run since CRLF line endings have been added: $ bash -x processes/script/executecommand.sh + $'\r' : command not foundecutecommand.sh: line 2: + $'\r' : command not foundecutecommand.sh: line 17: 'rocesses/script/executecommand.sh: line 30: syntax error near unexpected token `do 'rocesses/script/executecommand.sh: line 30: `for filename in $(ls -1 $MCF_HOME/processes/jar) ; do -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-189) Add the mail archive links to the mail.html page
[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13025533#comment-13025533 ] Karl Wright commented on CONNECTORS-189: Do you want to contribute a patch as well? It's not hard - the file is site/src/documentation/content/xdocs/mail.xml. There are other xml docs there that show how to do links in Forrest, if you grovel around. Add the mail archive links to the mail.html page Key: CONNECTORS-189 URL: https://issues.apache.org/jira/browse/CONNECTORS-189 Project: ManifoldCF Issue Type: Improvement Reporter: Farzad Priority: Minor I think this would best be added to the mail.html page, which describes the mail lists and how to sign up for them. Please feel free to open a jira ticket accordingly. Thanks! Karl On Tue, Apr 26, 2011 at 11:34 AM, conflue...@apache.org wrote: Space: Apache Connectors Framework (https://cwiki.apache.org/confluence/display/CONNECTORS) Page: FAQ (https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ) Comment: https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ?focusedCommentId=26119029#comment-26119029 Comment added by Farzad: - Found the root links, this is nice. Might want to add these to the FAQ. Do you know if there is a way to view snippets of the messages without having to click on each one? http://www.mail-archive.com/connectors-user@incubator.apache.org/index.html http://www.mail-archive.com/connectors-dev@incubator.apache.org/index.html http://www.mail-archive.com/general@incubator.apache.org/index.html In reply to a comment by Karl Wright: The news lists are in fact kept around; you can in fact use google to find old posts. Try googling ManifoldCF eclipse to see what I mean. Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-189) Add the mail archive links to the mail.html page
[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13025542#comment-13025542 ] Karl Wright commented on CONNECTORS-189: That looks about right. But you'll want to submit it in true patch form, and attach the patch to the ticket. Instructions for how to do that are in the How to contribute page of the wiki. Here's the link: https://cwiki.apache.org/confluence/display/CONNECTORS/HowToContribute Add the mail archive links to the mail.html page Key: CONNECTORS-189 URL: https://issues.apache.org/jira/browse/CONNECTORS-189 Project: ManifoldCF Issue Type: Improvement Reporter: Farzad Priority: Minor I think this would best be added to the mail.html page, which describes the mail lists and how to sign up for them. Please feel free to open a jira ticket accordingly. Thanks! Karl On Tue, Apr 26, 2011 at 11:34 AM, conflue...@apache.org wrote: Space: Apache Connectors Framework (https://cwiki.apache.org/confluence/display/CONNECTORS) Page: FAQ (https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ) Comment: https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ?focusedCommentId=26119029#comment-26119029 Comment added by Farzad: - Found the root links, this is nice. Might want to add these to the FAQ. Do you know if there is a way to view snippets of the messages without having to click on each one? http://www.mail-archive.com/connectors-user@incubator.apache.org/index.html http://www.mail-archive.com/connectors-dev@incubator.apache.org/index.html http://www.mail-archive.com/general@incubator.apache.org/index.html In reply to a comment by Karl Wright: The news lists are in fact kept around; you can in fact use google to find old posts. Try googling ManifoldCF eclipse to see what I mean. Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-189) Add the mail archive links to the mail.html page
[ https://issues.apache.org/jira/browse/CONNECTORS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-189: --- Resolution: Fixed Fix Version/s: (was: ManifoldCF 0.2) ManifoldCF next Assignee: Karl Wright Status: Resolved (was: Patch Available) Looks good. Committed - r1096998. Add the mail archive links to the mail.html page Key: CONNECTORS-189 URL: https://issues.apache.org/jira/browse/CONNECTORS-189 Project: ManifoldCF Issue Type: Improvement Affects Versions: ManifoldCF 0.2 Reporter: Farzad Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-189.patch, mail.xml I think this would best be added to the mail.html page, which describes the mail lists and how to sign up for them. Please feel free to open a jira ticket accordingly. Thanks! Karl On Tue, Apr 26, 2011 at 11:34 AM, conflue...@apache.org wrote: Space: Apache Connectors Framework (https://cwiki.apache.org/confluence/display/CONNECTORS) Page: FAQ (https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ) Comment: https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ?focusedCommentId=26119029#comment-26119029 Comment added by Farzad: - Found the root links, this is nice. Might want to add these to the FAQ. Do you know if there is a way to view snippets of the messages without having to click on each one? http://www.mail-archive.com/connectors-user@incubator.apache.org/index.html http://www.mail-archive.com/connectors-dev@incubator.apache.org/index.html http://www.mail-archive.com/general@incubator.apache.org/index.html In reply to a comment by Karl Wright: The news lists are in fact kept around; you can in fact use google to find old posts. Try googling ManifoldCF eclipse to see what I mean. Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-187) WorkerThread method processDeleteList does not handle ServiceInterruptions from output connector optimally
WorkerThread method processDeleteList does not handle ServiceInterruptions from output connector optimally -- Key: CONNECTORS-187 URL: https://issues.apache.org/jira/browse/CONNECTORS-187 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright The processDeleteList method in WorkerThread does not handle ServiceInterruption exceptions optimally; it just waits five minutes and retries. What it should do is requeue all the affected documents for the prescribed time, ignoring the possibility of failure or skip, since neither of these can be performed when the output connection is not working. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-183) SECURITY_AUTHENTICATION-changeable
[ https://issues.apache.org/jira/browse/CONNECTORS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-183: -- Assignee: Karl Wright SECURITY_AUTHENTICATION-changeable -- Key: CONNECTORS-183 URL: https://issues.apache.org/jira/browse/CONNECTORS-183 Project: ManifoldCF Issue Type: Improvement Components: Authority Service Affects Versions: ManifoldCF next Environment: Microsoft Windows Server 2003 R2 Microsoft Windows Server 2008 R2 Reporter: Shinichiro Abe Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-183.patch In ActiveDirectoryAuthority.java, env.put(Context.SECURITY_AUTHENTICATION,DIGEST-MD5 GSSAPI); Users may want to change the constant string. In my Windows2003/2008 environment, that does not work unless setting simple. Crawler-ui should allow users to the change authentication. See: http://java.sun.com/products/jndi/jndi-ldap-gl.html java.naming.security.authentication Direciton of improvement(at this time): Crawler-ui allows users to input AUTHENTICATION text value. ActiveDirectoryAuthority support none, simple and the authentication mechanism for the provider to use. ActiveDirectoryAuthority does not support strong, SASL authentication and SSL protocol. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-32) A general access-token cache within Authority Service would help performance
[ https://issues.apache.org/jira/browse/CONNECTORS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-32. --- Resolution: Fixed Fix Version/s: ManifoldCF next r1094217. A general access-token cache within Authority Service would help performance Key: CONNECTORS-32 URL: https://issues.apache.org/jira/browse/CONNECTORS-32 Project: ManifoldCF Issue Type: Improvement Components: Authority Service Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next We should consider adding user-keyed per-connector access token cache within LCF's authority service. Individual connectors should be able to signal how long their cached tokens survive. This would help enormously with the case where dozens of requests for the same user are submitted for every page in the end-user UI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-182) Timed cache invalidation does not work
[ https://issues.apache.org/jira/browse/CONNECTORS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-182. Resolution: Fixed Fix Version/s: ManifoldCF next r1094053. Timed cache invalidation does not work -- Key: CONNECTORS-182 URL: https://issues.apache.org/jira/browse/CONNECTORS-182 Project: ManifoldCF Issue Type: Bug Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next Timed cache invalidation does not work because the polling thread does not apparently manage to periodically call the cache manager to tell it to invalidate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
