[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-tabpanel&focusedCommentId=13041339#comment-13041339 ] Karl Wright commented on CONNECTORS-114: Just got email from the HSQLDB team, and confirmed that the deadlock issue was resolved in hsqldb 2.2.2. So it looks like we have a third database that ManifoldCF can work with. I've checked in the updated database jar, and am planning on writing a test series that uses hsqldb, much like the series that uses PostgreSQL. We've still got to settle on how precisely to do the equivalent of PostgreSQL's DISTINCT ON functionality, but that's all that is left. Also, FWIW, HSQLDB doesn't (as yet) seem to fail so spectacularly dealing with hopcounts as Derby does. > 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 > > 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] [Created] (CONNECTORS-203) Consider porting ManifoldCF to Java 1.5 code standards
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-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=13038477#comment-13038477 ] Karl Wright commented on CONNECTORS-202: An explicit commit is transmitted at the end of every job, and when a job is aborted, but I agree that that is not ideal. Your suggestion seems like a reasonable thing to add - probably on a new output specification tab, "Solr Commits" or some such. Pretty straightforward to code as well. Would you be interested in submitting a patch? > 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] [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-tabpanel&focusedCommentId=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-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] [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-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] [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-tabpanel&focusedCommentId=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-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] [Assigned] (CONNECTORS-199) Modify site release page to include new release
[ https://issues.apache.org/jira/browse/CONNECTORS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-199: -- Assignee: Karl Wright > 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 0.3 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.3 > > > 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] [Commented] (CONNECTORS-199) Modify site release page to include new release
[ https://issues.apache.org/jira/browse/CONNECTORS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034631#comment-13034631 ] Karl Wright commented on CONNECTORS-199: Also r1104055. > 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 0.3 >Reporter: Karl Wright > Fix For: ManifoldCF 0.3 > > > 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] [Resolved] (CONNECTORS-199) Modify site release page to include new release
[ https://issues.apache.org/jira/browse/CONNECTORS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-199. Resolution: Fixed Fix Version/s: ManifoldCF next r1104053. > 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 > Fix For: ManifoldCF next > > > 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-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] [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-tabpanel&focusedCommentId=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] [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] [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] [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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=13030669#comment-13030669 ] Karl Wright commented on CONNECTORS-197: In the patch, the following lines look incorrect: +"sAMAccountName\n"+ +"userPrincipalName\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] [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] [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] [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-tabpanel&focusedCommentId=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] [Updated] (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:all-tabpanel ] Karl Wright updated CONNECTORS-194: --- Resolution: Fixed Fix Version/s: ManifoldCF next Status: Resolved (was: Patch Available) r1100833 r1100835 > 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 > Fix For: ManifoldCF next > > 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-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-tabpanel&focusedCommentId=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-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-tabpanel&focusedCommentId=13030495#comment-13030495 ] Karl Wright commented on CONNECTORS-196: Cleaned things up with r1100743. > 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-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-tabpanel&focusedCommentId=13029914#comment-13029914 ] Karl Wright commented on CONNECTORS-197: External configuration of a connector should, in general, be avoided. The configuration information that would allow a user to choose between modes of operation should therefore be in ActiveDirectoryConfig, with corresponding Crawler UI functionality. > 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] [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-tabpanel&focusedCommentId=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] [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] [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] [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-tabpanel&focusedCommentId=13028610#comment-13028610 ] Karl Wright commented on CONNECTORS-195: I should also note that the original attached patch is INCORRECT, and should not be used. > 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] [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] [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-tabpanel&focusedCommentId=13028606#comment-13028606 ] Karl Wright commented on CONNECTORS-195: Every user in AD must have a SID, according to Microsoft documents for AD. If we find any user without a SID, the user does not exist. I checked in changes to that effect: r1099322. > 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] [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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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] [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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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] [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-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] [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] [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] [Resolved] (CONNECTORS-192) Job-related specification post method sometimes called without corresponding specification header/body
[ https://issues.apache.org/jira/browse/CONNECTORS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-192. Resolution: Fixed Fix Version/s: ManifoldCF next r1098419. > 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 > Fix For: ManifoldCF next > > > 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-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] [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-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] [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-tabpanel&focusedCommentId=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, 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] [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] [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] [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, 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-tabpanel&focusedCommentId=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, 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-tabpanel&focusedCommentId=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, 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] [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] [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] [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] [Resolved] (CONNECTORS-186) Output connector getOutputDescription() method does not throw a ServiceInterruption exception, but should
[ https://issues.apache.org/jira/browse/CONNECTORS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-186. Resolution: Fixed Fix Version/s: ManifoldCF next r1096386. > Output connector getOutputDescription() method does not throw a > ServiceInterruption exception, but should > - > > Key: CONNECTORS-186 > URL: https://issues.apache.org/jira/browse/CONNECTORS-186 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > The output connector interface does not permit the getOutputDescription() > method to throw a ServiceInterruption exception, but it should. It looks > like the only reason for this is because the control flow through the > WorkerThread class made it difficult to handle. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-186) Output connector getOutputDescription() method does not throw a ServiceInterruption exception, but should
Output connector getOutputDescription() method does not throw a ServiceInterruption exception, but should - Key: CONNECTORS-186 URL: https://issues.apache.org/jira/browse/CONNECTORS-186 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright The output connector interface does not permit the getOutputDescription() method to throw a ServiceInterruption exception, but it should. It looks like the only reason for this is because the control flow through the WorkerThread class made it difficult to handle. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-185) Multiprocess installation instructions do not include configuration file -D for web applications
[ https://issues.apache.org/jira/browse/CONNECTORS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023173#comment-13023173 ] Karl Wright commented on CONNECTORS-185: r1095899. > Multiprocess installation instructions do not include configuration file -D > for web applications > > > Key: CONNECTORS-185 > URL: https://issues.apache.org/jira/browse/CONNECTORS-185 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > Multiprocess installation instructions do not describe the configuration file > -D switch that's needed to point to the configuration file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-185) Multiprocess installation instructions do not include configuration file -D for web applications
[ https://issues.apache.org/jira/browse/CONNECTORS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-185. Resolution: Fixed Fix Version/s: ManifoldCF next > Multiprocess installation instructions do not include configuration file -D > for web applications > > > Key: CONNECTORS-185 > URL: https://issues.apache.org/jira/browse/CONNECTORS-185 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > Multiprocess installation instructions do not describe the configuration file > -D switch that's needed to point to the configuration file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-185) Multiprocess installation instructions do not include configuration file -D for web applications
Multiprocess installation instructions do not include configuration file -D for web applications Key: CONNECTORS-185 URL: https://issues.apache.org/jira/browse/CONNECTORS-185 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Multiprocess installation instructions do not describe the configuration file -D switch that's needed to point to the configuration file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-184) Active Directory authority could use support for SSL, and checkboxes/pulldowns for selection of authentication modes
[ https://issues.apache.org/jira/browse/CONNECTORS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-184: --- Component/s: (was: Authority Service) Active Directory authority > Active Directory authority could use support for SSL, and > checkboxes/pulldowns for selection of authentication modes > > > Key: CONNECTORS-184 > URL: https://issues.apache.org/jira/browse/CONNECTORS-184 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF next >Reporter: Karl Wright >Priority: Minor > > The active directory authority's UI or implementation currently does not > support SSL. Also, the selection of security protocol does not help the user > at all by giving any hints of what's allowed and what isn't - it's just a > simple text box. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-183) SECURITY_AUTHENTICATION-changeable
[ https://issues.apache.org/jira/browse/CONNECTORS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-183: --- Component/s: (was: Authority Service) Active Directory authority > SECURITY_AUTHENTICATION-changeable > -- > > Key: CONNECTORS-183 > URL: https://issues.apache.org/jira/browse/CONNECTORS-183 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >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] [Created] (CONNECTORS-184) Active Directory authority could use support for SSL, and checkboxes/pulldowns for selection of authentication modes
Active Directory authority could use support for SSL, and checkboxes/pulldowns for selection of authentication modes Key: CONNECTORS-184 URL: https://issues.apache.org/jira/browse/CONNECTORS-184 Project: ManifoldCF Issue Type: Improvement Components: Authority Service Affects Versions: ManifoldCF next Reporter: Karl Wright Priority: Minor The active directory authority's UI or implementation currently does not support SSL. Also, the selection of security protocol does not help the user at all by giving any hints of what's allowed and what isn't - it's just a simple text box. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-183) SECURITY_AUTHENTICATION-changeable
[ https://issues.apache.org/jira/browse/CONNECTORS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-183. Resolution: Fixed r1094993. > 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] [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] [Commented] (CONNECTORS-183) SECURITY_AUTHENTICATION-changeable
[ https://issues.apache.org/jira/browse/CONNECTORS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021414#comment-13021414 ] Karl Wright commented on CONNECTORS-183: Patch looks good to me. The only enhancement I can think of would be a series of checkboxes instead of a text field, listing all the available authentication protocols, if you know what these are. But we can cover that with another ticket. Please let me know how you want to proceed, and I'll commit this if you want to do it that way. > 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 >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
[jira] [Created] (CONNECTORS-182) Timed cache invalidation does not work
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 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
[jira] [Commented] (CONNECTORS-181) ICacheDescription's way of handling object expiration is very clumsy for fixed lifetime objects
[ https://issues.apache.org/jira/browse/CONNECTORS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020433#comment-13020433 ] Karl Wright commented on CONNECTORS-181: Also r1092813. > ICacheDescription's way of handling object expiration is very clumsy for > fixed lifetime objects > --- > > Key: CONNECTORS-181 > URL: https://issues.apache.org/jira/browse/CONNECTORS-181 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework core >Affects Versions: ManifoldCF next >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > The ICacheDescription getObjectExpirationTime() method works fine for the > model where each object access resets the expiration to some point in the > future, but it does not work well for the model where the object truly has a > fixed expiration time based on its creation time. This is interfering with > code for CONNECTORS-32. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-181) ICacheDescription's way of handling object expiration is very clumsy for fixed lifetime objects
[ https://issues.apache.org/jira/browse/CONNECTORS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-181. Resolution: Fixed Fix Version/s: ManifoldCF next r1092805. > ICacheDescription's way of handling object expiration is very clumsy for > fixed lifetime objects > --- > > Key: CONNECTORS-181 > URL: https://issues.apache.org/jira/browse/CONNECTORS-181 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework core >Affects Versions: ManifoldCF next >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > The ICacheDescription getObjectExpirationTime() method works fine for the > model where each object access resets the expiration to some point in the > future, but it does not work well for the model where the object truly has a > fixed expiration time based on its creation time. This is interfering with > code for CONNECTORS-32. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-181) ICacheDescription's way of handling object expiration is very clumsy for fixed lifetime objects
ICacheDescription's way of handling object expiration is very clumsy for fixed lifetime objects --- Key: CONNECTORS-181 URL: https://issues.apache.org/jira/browse/CONNECTORS-181 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright The ICacheDescription getObjectExpirationTime() method works fine for the model where each object access resets the expiration to some point in the future, but it does not work well for the model where the object truly has a fixed expiration time based on its creation time. This is interfering with code for CONNECTORS-32. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-179) IConnector interface method setThreadContext should throw ManifoldCFException, but doesn't
[ https://issues.apache.org/jira/browse/CONNECTORS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020240#comment-13020240 ] Karl Wright commented on CONNECTORS-179: And, r1092631. > IConnector interface method setThreadContext should throw > ManifoldCFException, but doesn't > -- > > Key: CONNECTORS-179 > URL: https://issues.apache.org/jira/browse/CONNECTORS-179 > Project: ManifoldCF > Issue Type: Bug > Components: Framework core >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > The IConnector method setThreadContext does not throw ManifoldCFException. > This makes it very difficult to use the method for its intended purpose, > which is to set up handles that are thread-context dependent. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-180) Connector factories all have a Pool class that should be derived from a base Pool class
Connector factories all have a Pool class that should be derived from a base Pool class --- Key: CONNECTORS-180 URL: https://issues.apache.org/jira/browse/CONNECTORS-180 Project: ManifoldCF Issue Type: Improvement Components: Framework core Reporter: Karl Wright Priority: Minor There's a fair bit of duplicated code in the connector factories - RepositoryConnectorFactory, AuthorityConnectorFactory, etc. The duplicated code can be easily eliminated by creating a base factory pool class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-179) IConnector interface method setThreadContext should throw ManifoldCFException, but doesn't
[ https://issues.apache.org/jira/browse/CONNECTORS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020163#comment-13020163 ] Karl Wright commented on CONNECTORS-179: Also r1092568. > IConnector interface method setThreadContext should throw > ManifoldCFException, but doesn't > -- > > Key: CONNECTORS-179 > URL: https://issues.apache.org/jira/browse/CONNECTORS-179 > Project: ManifoldCF > Issue Type: Bug > Components: Framework core >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > The IConnector method setThreadContext does not throw ManifoldCFException. > This makes it very difficult to use the method for its intended purpose, > which is to set up handles that are thread-context dependent. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-179) IConnector interface method setThreadContext should throw ManifoldCFException, but doesn't
[ https://issues.apache.org/jira/browse/CONNECTORS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-179. Resolution: Fixed Fix Version/s: ManifoldCF next r1092566 > IConnector interface method setThreadContext should throw > ManifoldCFException, but doesn't > -- > > Key: CONNECTORS-179 > URL: https://issues.apache.org/jira/browse/CONNECTORS-179 > Project: ManifoldCF > Issue Type: Bug > Components: Framework core >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > The IConnector method setThreadContext does not throw ManifoldCFException. > This makes it very difficult to use the method for its intended purpose, > which is to set up handles that are thread-context dependent. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-179) IConnector interface method setThreadContext should throw ManifoldCFException, but doesn't
IConnector interface method setThreadContext should throw ManifoldCFException, but doesn't -- Key: CONNECTORS-179 URL: https://issues.apache.org/jira/browse/CONNECTORS-179 Project: ManifoldCF Issue Type: Bug Components: Framework core Reporter: Karl Wright Assignee: Karl Wright The IConnector method setThreadContext does not throw ManifoldCFException. This makes it very difficult to use the method for its intended purpose, which is to set up handles that are thread-context dependent. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-71) Document Memex connector configuration/specification/command API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-71. --- Resolution: Won't Fix Fix Version/s: ManifoldCF 0.1 Memex is no longer included because of objections by the Memex, Ltd. > Document Memex connector configuration/specification/command API pieces > --- > > Key: CONNECTORS-71 > URL: https://issues.apache.org/jira/browse/CONNECTORS-71 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Reporter: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.1 > > > Need to document Memex connector - specific API objects and commands. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-93) add contributors to CHANGES.txt
[ https://issues.apache.org/jira/browse/CONNECTORS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-93. --- Resolution: Fixed Fix Version/s: ManifoldCF 0.1 Assignee: Robert Muir Ticket was completed long ago. > add contributors to CHANGES.txt > --- > > Key: CONNECTORS-93 > URL: https://issues.apache.org/jira/browse/CONNECTORS-93 > Project: ManifoldCF > Issue Type: Task > Components: Documentation >Reporter: Robert Muir >Assignee: Robert Muir > Fix For: ManifoldCF 0.1 > > Attachments: CONNECTORS-93.patch > > > As mentioned on the connectors-dev@ list (change the format of CHANGES.txt), > I propose we modify CHANGES.txt > to give credit to contributors who have given bug reports, comments, patches, > etc. > I'll volunteer to go thru the mail archives and jira issues that are marked > 'resolved' and upload a patch here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-175) The site documentation property list does not include the PostgreSQL-specific parameters, and may be missing some of the Derby ones too
[ https://issues.apache.org/jira/browse/CONNECTORS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-175. Resolution: Fixed Fix Version/s: ManifoldCF next r1089704. > The site documentation property list does not include the PostgreSQL-specific > parameters, and may be missing some of the Derby ones too > --- > > Key: CONNECTORS-175 > URL: https://issues.apache.org/jira/browse/CONNECTORS-175 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF next >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF next > > > The table that documents all the properties in properties.xml seems to be > missing the PostgreSQL-specific ones. This is the > how-to-build-and-deploy.html page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-175) The site documentation property list does not include the PostgreSQL-specific parameters, and may be missing some of the Derby ones too
[ https://issues.apache.org/jira/browse/CONNECTORS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-175: -- Assignee: Karl Wright > The site documentation property list does not include the PostgreSQL-specific > parameters, and may be missing some of the Derby ones too > --- > > Key: CONNECTORS-175 > URL: https://issues.apache.org/jira/browse/CONNECTORS-175 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF next >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Minor > > The table that documents all the properties in properties.xml seems to be > missing the PostgreSQL-specific ones. This is the > how-to-build-and-deploy.html page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-175) The site documentation property list does not include the PostgreSQL-specific parameters, and may be missing some of the Derby ones too
[ https://issues.apache.org/jira/browse/CONNECTORS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016641#comment-13016641 ] Karl Wright commented on CONNECTORS-175: The QuickStart parameters org.apache.manifoldcf.dbsuperusername and org.apache.manifoldcf.dbsuperuserpassword are definitely missing. > The site documentation property list does not include the PostgreSQL-specific > parameters, and may be missing some of the Derby ones too > --- > > Key: CONNECTORS-175 > URL: https://issues.apache.org/jira/browse/CONNECTORS-175 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF next >Reporter: Karl Wright >Priority: Minor > > The table that documents all the properties in properties.xml seems to be > missing the PostgreSQL-specific ones. This is the > how-to-build-and-deploy.html page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-118) Crawled archive files should be expanded into their constituent files
[ https://issues.apache.org/jira/browse/CONNECTORS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015438#comment-13015438 ] Karl Wright commented on CONNECTORS-118: I just ran into a convention that (apparently) slf4j uses for archive files: [jar:file:/opt/ovi/search/servlet/tomcat/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] I don't know how universal this is but it deserves exploration. > Crawled archive files should be expanded into their constituent files > - > > Key: CONNECTORS-118 > URL: https://issues.apache.org/jira/browse/CONNECTORS-118 > Project: ManifoldCF > Issue Type: New Feature > Components: File system connector, JCIFS connector, Web connector >Reporter: Jack Krupansky > > Archive files such as zip, mbox, tar, etc. should be expanded into their > constituent files during crawling of repositories so that any output > connector would output the flattened archive. > This could be an option, defaulted to ON, since someone may want to implement > a "copy" connector that maintains crawled files as-is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-55) Bundle database server with ManifoldCF packaged product
[ https://issues.apache.org/jira/browse/CONNECTORS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015029#comment-13015029 ] Karl Wright commented on CONNECTORS-55: --- Correction: QuickStart with Derby cannot be run in multiprocess mode, because you cannot currently configure ManifoldCF to use the Derby client JDBC driver. See CONNECTORS-178. > Bundle database server with ManifoldCF packaged product > --- > > Key: CONNECTORS-55 > URL: https://issues.apache.org/jira/browse/CONNECTORS-55 > Project: ManifoldCF > Issue Type: Sub-task > Components: Installers >Reporter: Jack Krupansky > > The current requirement that the user install and deploy a PostgreSQL server > complicates the installation and deployment of LCF for the user. Installation > and deployment of LCF should be as simple as Solr itself. QuickStart is great > for the low-end and basic evaluation, but a comparable level of simplified > installation and deployment is still needed for full-blown, high-end > environments that need the full performance of a ProstgreSQL-class database > server. So, PostgreSQL should be bundled with the packaged release of LCF so > that installation and deployment of LCF will automatically install and deploy > a subset of the full PostgreSQL distribution that is sufficient for the needs > of LCF. Starting LCF, with or without the LCF UI, should automatically start > the database server. Shutting down LCF should also shutdown the database > server process. > A typical use case would be for a non-developer who is comfortable with Solr > and simply wants to crawl documents from, for example, a SharePoint > repository and feed them into Solr. QuickStart should work well for the low > end or in the early stages of evaluation, but the user would prefer to > evaluate "the real thing" with something resembling a production crawl of > thousands of documents. Such a user might not be a hard-core developer or be > comfortable fiddling with a lot of software components simply to do one > conceptually simple operation. > It should still be possible for the user to supply database server settings > to override the defaults, but the LCF package should have all of the > best-practice settings deemed appropriate for use with LCF. > One downside is that installation and deployment will be platform-specific > since there are multiple processes and PostgreSQL itself requires a > platform-specific installation. > This proposal presumes that PostgreSQL is the best option for the foreseeable > future, but nothing here is intended to preclude support for other database > servers in futures releases. > This proposal should not have any impact on QuickStart packaging or > deployment. > Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-178) Implement ability to run ManifoldCF with Derby in multiprocess mode
Implement ability to run ManifoldCF with Derby in multiprocess mode --- Key: CONNECTORS-178 URL: https://issues.apache.org/jira/browse/CONNECTORS-178 Project: ManifoldCF Issue Type: Bug Components: Documentation, Framework core Reporter: Karl Wright Priority: Minor Derby has a standalone server mode, which we can no doubt use if we modify the Derby driver to accept a configuration parameter which allows you to choose between the embedded driver and the client driver. It might be useful to be able to run ManifoldCF with Derby in this manner. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-177) File System Connector has some testing code in it
File System Connector has some testing code in it - Key: CONNECTORS-177 URL: https://issues.apache.org/jira/browse/CONNECTORS-177 Project: ManifoldCF Issue Type: Improvement Components: File system connector Affects Versions: ManifoldCF next Reporter: Karl Wright Priority: Minor The file system connector has testing code in it that should be removed. See getBinNames(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-120) Port all connectors to use httpclient 4.x, after we submit our remaining 3.x changes as commons-httpclient tickets
[ https://issues.apache.org/jira/browse/CONNECTORS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-120: --- Summary: Port all connectors to use httpclient 4.x, after we submit our remaining 3.x changes as commons-httpclient tickets (was: Port all connectors to use httpclient 4.x, after it is released with full NTLM support) > Port all connectors to use httpclient 4.x, after we submit our remaining 3.x > changes as commons-httpclient tickets > -- > > Key: CONNECTORS-120 > URL: https://issues.apache.org/jira/browse/CONNECTORS-120 > Project: ManifoldCF > Issue Type: Task > Components: LiveLink connector, Meridio connector, RSS connector, > SharePoint connector, Web connector >Reporter: Karl Wright > > Now that commons-httpclient has accepted our NTLM patch, we can upgrade our > connectors to use their newest 4.x httpclient code. We still need to submit > or apply patches for other features first, so this ticket depends on the > resolution of that action, covered in CONNECTORS-119. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-55) Bundle database server with ManifoldCF packaged product
[ https://issues.apache.org/jira/browse/CONNECTORS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-55: -- Summary: Bundle database server with ManifoldCF packaged product (was: Bundle database server with LCF packaged product) > Bundle database server with ManifoldCF packaged product > --- > > Key: CONNECTORS-55 > URL: https://issues.apache.org/jira/browse/CONNECTORS-55 > Project: ManifoldCF > Issue Type: Sub-task > Components: Installers >Reporter: Jack Krupansky > > The current requirement that the user install and deploy a PostgreSQL server > complicates the installation and deployment of LCF for the user. Installation > and deployment of LCF should be as simple as Solr itself. QuickStart is great > for the low-end and basic evaluation, but a comparable level of simplified > installation and deployment is still needed for full-blown, high-end > environments that need the full performance of a ProstgreSQL-class database > server. So, PostgreSQL should be bundled with the packaged release of LCF so > that installation and deployment of LCF will automatically install and deploy > a subset of the full PostgreSQL distribution that is sufficient for the needs > of LCF. Starting LCF, with or without the LCF UI, should automatically start > the database server. Shutting down LCF should also shutdown the database > server process. > A typical use case would be for a non-developer who is comfortable with Solr > and simply wants to crawl documents from, for example, a SharePoint > repository and feed them into Solr. QuickStart should work well for the low > end or in the early stages of evaluation, but the user would prefer to > evaluate "the real thing" with something resembling a production crawl of > thousands of documents. Such a user might not be a hard-core developer or be > comfortable fiddling with a lot of software components simply to do one > conceptually simple operation. > It should still be possible for the user to supply database server settings > to override the defaults, but the LCF package should have all of the > best-practice settings deemed appropriate for use with LCF. > One downside is that installation and deployment will be platform-specific > since there are multiple processes and PostgreSQL itself requires a > platform-specific installation. > This proposal presumes that PostgreSQL is the best option for the foreseeable > future, but nothing here is intended to preclude support for other database > servers in futures releases. > This proposal should not have any impact on QuickStart packaging or > deployment. > Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-55) Bundle database server with LCF packaged product
[ https://issues.apache.org/jira/browse/CONNECTORS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015021#comment-13015021 ] Karl Wright commented on CONNECTORS-55: --- The current status of this feature request is as follows: - There is a Quick Start, which can run either with Derby or with PostgreSQL, depending on what you put in connectors.xml. - We've done a lot of fixes to the Derby support, although there are two outstanding tickets that need to be resolved before it can be considered "real". See CONNECTORS-100 and CONNECTORS-110. - You can run the Quick Start with embedded Derby in a mode that allows external connections. "java -Dderby.drda.startNetworkServer=true -jar start.jar". If you want a truly multiprocess ManifoldCF running, you will also need to set up file-based synchronization, as described in how-to-build-and-deploy.html. - Instructions for how to run Quick Start with PostgreSQL are in the FAQ. - I coded an HSQLDB implementation, but that's stalled because HSQLDB internally deadlocks. See CONNECTORS-114. - Nobody has looked at H2 in any depth yet. Not clear if we still need to. > Bundle database server with LCF packaged product > > > Key: CONNECTORS-55 > URL: https://issues.apache.org/jira/browse/CONNECTORS-55 > Project: ManifoldCF > Issue Type: Sub-task > Components: Installers >Reporter: Jack Krupansky > > The current requirement that the user install and deploy a PostgreSQL server > complicates the installation and deployment of LCF for the user. Installation > and deployment of LCF should be as simple as Solr itself. QuickStart is great > for the low-end and basic evaluation, but a comparable level of simplified > installation and deployment is still needed for full-blown, high-end > environments that need the full performance of a ProstgreSQL-class database > server. So, PostgreSQL should be bundled with the packaged release of LCF so > that installation and deployment of LCF will automatically install and deploy > a subset of the full PostgreSQL distribution that is sufficient for the needs > of LCF. Starting LCF, with or without the LCF UI, should automatically start > the database server. Shutting down LCF should also shutdown the database > server process. > A typical use case would be for a non-developer who is comfortable with Solr > and simply wants to crawl documents from, for example, a SharePoint > repository and feed them into Solr. QuickStart should work well for the low > end or in the early stages of evaluation, but the user would prefer to > evaluate "the real thing" with something resembling a production crawl of > thousands of documents. Such a user might not be a hard-core developer or be > comfortable fiddling with a lot of software components simply to do one > conceptually simple operation. > It should still be possible for the user to supply database server settings > to override the defaults, but the LCF package should have all of the > best-practice settings deemed appropriate for use with LCF. > One downside is that installation and deployment will be platform-specific > since there are multiple processes and PostgreSQL itself requires a > platform-specific installation. > This proposal presumes that PostgreSQL is the best option for the foreseeable > future, but nothing here is intended to preclude support for other database > servers in futures releases. > This proposal should not have any impact on QuickStart packaging or > deployment. > Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-27) Add support for observation to the crawler agent
[ https://issues.apache.org/jira/browse/CONNECTORS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015020#comment-13015020 ] Karl Wright commented on CONNECTORS-27: --- This ticket is stalled; it needed clarification as to the use case. > Add support for observation to the crawler agent > > > Key: CONNECTORS-27 > URL: https://issues.apache.org/jira/browse/CONNECTORS-27 > Project: ManifoldCF > Issue Type: New Feature > Components: Framework crawler agent >Reporter: Ralph Benjamin Ruijs >Priority: Minor > Attachments: Added_observation_logic_to_the_crawler.patch > > > When crawling a large repository, it could take a lot of time before changes > are propagated to Solr. You can add an event listener to the repository, and > be notified about changes. The crawler will ensure you have a complete copy > in case of missed events. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-118) Crawled archive files should be expanded into their constituent files
[ https://issues.apache.org/jira/browse/CONNECTORS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-118: --- Component/s: (was: Framework crawler agent) Web connector JCIFS connector File system connector > Crawled archive files should be expanded into their constituent files > - > > Key: CONNECTORS-118 > URL: https://issues.apache.org/jira/browse/CONNECTORS-118 > Project: ManifoldCF > Issue Type: New Feature > Components: File system connector, JCIFS connector, Web connector >Reporter: Jack Krupansky > > Archive files such as zip, mbox, tar, etc. should be expanded into their > constituent files during crawling of repositories so that any output > connector would output the flattened archive. > This could be an option, defaulted to ON, since someone may want to implement > a "copy" connector that maintains crawled files as-is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-118) Crawled archive files should be expanded into their constituent files
[ https://issues.apache.org/jira/browse/CONNECTORS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015019#comment-13015019 ] Karl Wright commented on CONNECTORS-118: This ticket is stalled. The driver behind it was being able to support a feature that Aperture has. The way it would need to be done in ManifoldCF is to have individual connectors deal with the feature. Each connector that supports it would know how to generate a specialized URL which referred to the archive contents, and the document identifiers for such connectors would also need to be changed to be able to represent archive contents as well. The connectors under consideration would be the file system connector, the JCIFS connector, and the Web connector. > Crawled archive files should be expanded into their constituent files > - > > Key: CONNECTORS-118 > URL: https://issues.apache.org/jira/browse/CONNECTORS-118 > Project: ManifoldCF > Issue Type: New Feature > Components: Framework crawler agent >Reporter: Jack Krupansky > > Archive files such as zip, mbox, tar, etc. should be expanded into their > constituent files during crawling of repositories so that any output > connector would output the flattened archive. > This could be an option, defaulted to ON, since someone may want to implement > a "copy" connector that maintains crawled files as-is. -- 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-tabpanel&focusedCommentId=13015015#comment-13015015 ] Karl Wright commented on CONNECTORS-110: This ticket is stalled because it requires a new Derby feature to resolve. The resolution will be to assess the current version of Derby and find out whether the required feature has been added, and barring that, opening a Derby ticket for the feature. > 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
[ 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 (was: Max activity and Max bandwidth reports fail under Derby with a stack trace) > 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] [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-tabpanel&focusedCommentId=13015013#comment-13015013 ] Karl Wright commented on CONNECTORS-114: This is stalled, because HSQLDB is not yet ready for the kinds of demands that ManifoldCF will put on it. Working with Derby seems more appropriate since they've been able to respond to bugs. > 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 > > 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-58) ManifoldCF scripting language, executed via the API, plus "example" jobs for file system and web crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-58: -- Summary: ManifoldCF scripting language, executed via the API, plus "example" jobs for file system and web crawl (was: ManifoldCF scripting language and some example scripts, executed via the API, plus "example" jobs for file system and web crawl ) > ManifoldCF scripting language, executed via the API, plus "example" jobs for > file system and web crawl > --- > > Key: CONNECTORS-58 > URL: https://issues.apache.org/jira/browse/CONNECTORS-58 > Project: ManifoldCF > Issue Type: Sub-task > Components: Examples >Reporter: Jack Krupansky >Priority: Minor > > Creating a basic connection setup to do a relatively simple crawl for a file > system or web can be a daunting task for someone new to LCF. So, it would be > nice to have a scripting file that supports an abbreviated API (subset of the > full API discussed in CONNECTORS-56) sufficient to create a default set of > connections and example jobs that the new user can choose from. > Beyond this initial need, this script format might be a useful form to "dump" > all of the connections and jobs in the LCF database in a form that can be > used to recreate an LCF configuration. Kind of a "dump and reload" > capability. That in fact might be how the initial example script gets created. > Those are two distinct use cases, but could utilize the same feature. > The example script could have example jobs to crawl a subdirectory of LCF, > crawl the LCF wiki, etc. > There could be more than one script. There might be example scripts for each > form of connector. > This capability should be available for both QuickStart and the general > release of LCF. > As just one possibility, the script format might be a sequence of JSON > expressions, each with an initial string analogous to a servlet path to > specify the operation to be performed, followed by the JSON form of the > connection or job or other LCF object. Or, some other format might be more > suitable. > Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-58) ManifoldCF scripting language and some example scripts, executed via the API, plus "example" jobs for file system and web crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-58: -- Summary: ManifoldCF scripting language and some example scripts, executed via the API, plus "example" jobs for file system and web crawl (was: Mini-API to initially configure default connections and "example" jobs for file system and web crawl ) > ManifoldCF scripting language and some example scripts, executed via the API, > plus "example" jobs for file system and web crawl > > > Key: CONNECTORS-58 > URL: https://issues.apache.org/jira/browse/CONNECTORS-58 > Project: ManifoldCF > Issue Type: Sub-task > Components: Examples >Reporter: Jack Krupansky >Priority: Minor > > Creating a basic connection setup to do a relatively simple crawl for a file > system or web can be a daunting task for someone new to LCF. So, it would be > nice to have a scripting file that supports an abbreviated API (subset of the > full API discussed in CONNECTORS-56) sufficient to create a default set of > connections and example jobs that the new user can choose from. > Beyond this initial need, this script format might be a useful form to "dump" > all of the connections and jobs in the LCF database in a form that can be > used to recreate an LCF configuration. Kind of a "dump and reload" > capability. That in fact might be how the initial example script gets created. > Those are two distinct use cases, but could utilize the same feature. > The example script could have example jobs to crawl a subdirectory of LCF, > crawl the LCF wiki, etc. > There could be more than one script. There might be example scripts for each > form of connector. > This capability should be available for both QuickStart and the general > release of LCF. > As just one possibility, the script format might be a sequence of JSON > expressions, each with an initial string analogous to a servlet path to > specify the operation to be performed, followed by the JSON form of the > connection or job or other LCF object. Or, some other format might be more > suitable. > Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-58) Mini-API to initially configure default connections and "example" jobs for file system and web crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015010#comment-13015010 ] Karl Wright commented on CONNECTORS-58: --- This ticket is currently stalled. I think the actual feature that would address it would be a ManifoldCF scripting client, so one could execute ManifoldCF scripts that would run via the ManifoldCF API. Then, example scripts could be easily added. This could be an entertaining project and might easily be useful for testing as well. > Mini-API to initially configure default connections and "example" jobs for > file system and web crawl > - > > Key: CONNECTORS-58 > URL: https://issues.apache.org/jira/browse/CONNECTORS-58 > Project: ManifoldCF > Issue Type: Sub-task > Components: Examples >Reporter: Jack Krupansky >Priority: Minor > > Creating a basic connection setup to do a relatively simple crawl for a file > system or web can be a daunting task for someone new to LCF. So, it would be > nice to have a scripting file that supports an abbreviated API (subset of the > full API discussed in CONNECTORS-56) sufficient to create a default set of > connections and example jobs that the new user can choose from. > Beyond this initial need, this script format might be a useful form to "dump" > all of the connections and jobs in the LCF database in a form that can be > used to recreate an LCF configuration. Kind of a "dump and reload" > capability. That in fact might be how the initial example script gets created. > Those are two distinct use cases, but could utilize the same feature. > The example script could have example jobs to crawl a subdirectory of LCF, > crawl the LCF wiki, etc. > There could be more than one script. There might be example scripts for each > form of connector. > This capability should be available for both QuickStart and the general > release of LCF. > As just one possibility, the script format might be a sequence of JSON > expressions, each with an initial string analogous to a servlet path to > specify the operation to be performed, followed by the JSON form of the > connection or job or other LCF object. Or, some other format might be more > suitable. > Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-92) Move from ant to maven or other build system with decent library management
[ https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015008#comment-13015008 ] Karl Wright commented on CONNECTORS-92: --- This issue has stalled. The work done so far has created a reasonable directory structure with a pom.xml everywhere it needs to be. However, beyond that, nothing more has happened. It might be worth researching ant with ivy at this point, since that would be a natural extension of the current built system, rather than trying to go the maven route entirely. > Move from ant to maven or other build system with decent library management > --- > > Key: CONNECTORS-92 > URL: https://issues.apache.org/jira/browse/CONNECTORS-92 > Project: ManifoldCF > Issue Type: Wish > Components: Build >Reporter: Jettro Coenradie >Assignee: Karl Wright > Attachments: Screen shot 2010-08-23 at 16.31.07.png, > maven-poms-including-start-jar.patch, > maven-poms-problem-starting-jetty-and-derby.patch, maven-start-jar.patch, > move-to-maven-acf-framework.patch, patch-connectors.zip > > > I am looking at the current project structure. If we want to make another > build tool available I think we need to change the directory structure. I > tried to place a suggestion in an image. Can you please have a look at it. If > we agree that this is a good way to go, than I will continue to work on a > patch. Which might be a bit hard with all these changing directories, but > I'll do my best to at least get an idea whether it would be working. > So I have three questions: > - Do you want to move to maven or put maven next to ant? > - Do you prefer another build mechanism [ant with ivy, gradle, maven3] > - Do you have an idea about the amount of scripts that need to be changed if > we change the project structure > The image of a possible project layout (that is based on the maven standards) > is attached to the issue -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-92) Move from ant to maven or other build system with decent library management
[ https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015008#comment-13015008 ] Karl Wright edited comment on CONNECTORS-92 at 4/2/11 11:47 AM: This issue has stalled. The work done so far has created a reasonable directory structure with a pom.xml everywhere it needs to be. However, beyond that, nothing more has happened. It might be worth researching ant with ivy at this point, since that would be a natural extension of the current build system, rather than trying to go the maven route entirely. was (Author: kwri...@metacarta.com): This issue has stalled. The work done so far has created a reasonable directory structure with a pom.xml everywhere it needs to be. However, beyond that, nothing more has happened. It might be worth researching ant with ivy at this point, since that would be a natural extension of the current built system, rather than trying to go the maven route entirely. > Move from ant to maven or other build system with decent library management > --- > > Key: CONNECTORS-92 > URL: https://issues.apache.org/jira/browse/CONNECTORS-92 > Project: ManifoldCF > Issue Type: Wish > Components: Build >Reporter: Jettro Coenradie >Assignee: Karl Wright > Attachments: Screen shot 2010-08-23 at 16.31.07.png, > maven-poms-including-start-jar.patch, > maven-poms-problem-starting-jetty-and-derby.patch, maven-start-jar.patch, > move-to-maven-acf-framework.patch, patch-connectors.zip > > > I am looking at the current project structure. If we want to make another > build tool available I think we need to change the directory structure. I > tried to place a suggestion in an image. Can you please have a look at it. If > we agree that this is a good way to go, than I will continue to work on a > patch. Which might be a bit hard with all these changing directories, but > I'll do my best to at least get an idea whether it would be working. > So I have three questions: > - Do you want to move to maven or put maven next to ant? > - Do you prefer another build mechanism [ant with ivy, gradle, maven3] > - Do you have an idea about the amount of scripts that need to be changed if > we change the project structure > The image of a possible project layout (that is based on the maven standards) > is attached to the issue -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
