[jira] [Commented] (CONNECTORS-248) File system crawl with HSQLDB aborts with a constraint error
[ https://issues.apache.org/jira/browse/CONNECTORS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095217#comment-13095217 ] Karl Wright commented on CONNECTORS-248: Talked with Fred Toussi about this. He's looked at the HSQLDB database settings, and has the following comment: Your settings indicate this should not have happened. If this is caused by a race condition or similar in the database engine, switching the trasaction isolation model from MVCC to LOCKS would prevent it. I would recommend this as a temprary fix for your v. 0.3 until I find the cause. Regards Fred I'm going to wait a bit to see what he comes up with. File system crawl with HSQLDB aborts with a constraint error Key: CONNECTORS-248 URL: https://issues.apache.org/jira/browse/CONNECTORS-248 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright While running two jobs with overlapping files with HSQLDB, I got this error on the second job that aborted it: Error: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS The complete exception is here: ERROR 2011-08-31 21:07:06,029 (Worker thread '34') - Exception tossed: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS org.apache.manifoldcf.core.interfaces.ManifoldCFException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.reinterpretException(DBInterfaceHSQLDB.java:587) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performModification(DBInterfaceHSQLDB.java:607) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performUpdate(DBInterfaceHSQLDB.java:242) at org.apache.manifoldcf.core.database.BaseTable.performUpdate(BaseTable.java:88) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.updateRowIds(IncrementalIngester.java:628) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentCheckMultiple(IncrementalIngester.java:588) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:653) Caused by: java.sql.SQLException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.jdbc.Util.sqlException(Util.java:255) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4659) at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(JDBCPreparedStatement.java:311) at org.apache.manifoldcf.core.database.Database.execute(Database.java:606) at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421) Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.error.Error.error(Error.java:134) at org.hsqldb.Constraint.getException(Constraint.java:914) at org.hsqldb.index.IndexAVL.insert(IndexAVL.java:731) at org.hsqldb.persist.RowStoreAVL.indexRow(RowStoreAVL.java:171) at org.hsqldb.persist.RowStoreAVLDisk.indexRow(RowStoreAVLDisk.java:169) at org.hsqldb.TransactionManagerMVCC.addInsertAction(TransactionManagerMVCC.java:401) at org.hsqldb.Session.addInsertAction(Session.java:434) at org.hsqldb.Table.insertSingleRow(Table.java:2553) at org.hsqldb.StatementDML.update(StatementDML.java:1032) at org.hsqldb.StatementDML.executeUpdateStatement(StatementDML.java:541) at org.hsqldb.StatementDML.getResult(StatementDML.java:196) at org.hsqldb.StatementDMQL.execute(StatementDMQL.java:190) at org.hsqldb.Session.executeCompiledStatement(Session.java:1340) at org.hsqldb.Session.execute(Session.java:993) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4651) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-164) Support Oracle for DBInterface
[ https://issues.apache.org/jira/browse/CONNECTORS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-164: --- Component/s: (was: API) Framework core Affects Version/s: ManifoldCF 0.2 Support Oracle for DBInterface -- Key: CONNECTORS-164 URL: https://issues.apache.org/jira/browse/CONNECTORS-164 Project: ManifoldCF Issue Type: New Feature Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Jeff Guo Fix For: ManifoldCF next Original Estimate: 504h Remaining Estimate: 504h The DBInterface currently supports PostgreSQL, Derby, and MySql, Oracle support is needed as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-164) Support Oracle for DBInterface
[ https://issues.apache.org/jira/browse/CONNECTORS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-164: --- Fix Version/s: ManifoldCF next Support Oracle for DBInterface -- Key: CONNECTORS-164 URL: https://issues.apache.org/jira/browse/CONNECTORS-164 Project: ManifoldCF Issue Type: New Feature Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Jeff Guo Fix For: ManifoldCF next Original Estimate: 504h Remaining Estimate: 504h The DBInterface currently supports PostgreSQL, Derby, and MySql, Oracle support is needed as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-158) SharePoint 2010 evaluation needed; possible changes and removal of custom web service for this version
[ https://issues.apache.org/jira/browse/CONNECTORS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-158: --- Fix Version/s: ManifoldCF next SharePoint 2010 evaluation needed; possible changes and removal of custom web service for this version -- Key: CONNECTORS-158 URL: https://issues.apache.org/jira/browse/CONNECTORS-158 Project: ManifoldCF Issue Type: Improvement Components: SharePoint connector Affects Versions: ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next We need to evaluate the SharePoint connector against SharePoint 2010. The goal would be to see if it works, and also to see if Microsoft provides functionality that would make the deployment of the custom MCPermissions web service unnecessary for this version of SharePoint. Modifications may be necessary or desired based on what the research indicates. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-79) Tests and test server for jCIFS connector needed
[ https://issues.apache.org/jira/browse/CONNECTORS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-79: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Issue Type: Test (was: Bug) Tests and test server for jCIFS connector needed Key: CONNECTORS-79 URL: https://issues.apache.org/jira/browse/CONNECTORS-79 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next We need test infrastructure and tests for the jCIFS connector. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-83) Tests and test server needed for Meridio connector
[ https://issues.apache.org/jira/browse/CONNECTORS-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-83: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Tests and test server needed for Meridio connector -- Key: CONNECTORS-83 URL: https://issues.apache.org/jira/browse/CONNECTORS-83 Project: ManifoldCF Issue Type: Bug Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next The Meridio connector needs tests, and a Meridio test server to run against. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-82) Tests and test server needed for Memex connector
[ https://issues.apache.org/jira/browse/CONNECTORS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-82: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Issue Type: Test (was: Bug) Tests and test server needed for Memex connector Key: CONNECTORS-82 URL: https://issues.apache.org/jira/browse/CONNECTORS-82 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next The Memex connector needs tests and a Patriarch server to run against. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-84) Tests and test server needed for SharePoint connector
[ https://issues.apache.org/jira/browse/CONNECTORS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-84: -- Component/s: (was: SharePoint connector) Tests Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Issue Type: Test (was: Bug) Tests and test server needed for SharePoint connector - Key: CONNECTORS-84 URL: https://issues.apache.org/jira/browse/CONNECTORS-84 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next We need tests and a SharePoint server to test the SharePoint connector. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-77) Tests and test server needed for FileNet connector
[ https://issues.apache.org/jira/browse/CONNECTORS-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-77: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Issue Type: Test (was: Bug) Tests and test server needed for FileNet connector -- Key: CONNECTORS-77 URL: https://issues.apache.org/jira/browse/CONNECTORS-77 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next We need global testing infrastructure available that would permit a FileNet test to be written. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-87) Connector Framework load test needs to be written
[ https://issues.apache.org/jira/browse/CONNECTORS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-87: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Issue Type: Test (was: Bug) Connector Framework load test needs to be written - Key: CONNECTORS-87 URL: https://issues.apache.org/jira/browse/CONNECTORS-87 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next LCF needs a load or performance test, which verifies that the core software is performing as expected. This test can use the file system connector, but must verify that individual throttle bins are getting approximately equal time, and that the system as a whole is behaving efficiently. Furthermore, at least 1,000,000 documents should be crawled by this test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095233#comment-13095233 ] Emmanuel Keller commented on CONNECTORS-240: I hope to be able to provide the content in the next few days. Not later than the beginning of the next week. OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Attachments: oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-13) We should move to eliminate process synchronization via shared file system, and use a process/service instead
[ https://issues.apache.org/jira/browse/CONNECTORS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-13: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Remaining Estimate: (was: 168h) Original Estimate: (was: 168h) We should move to eliminate process synchronization via shared file system, and use a process/service instead - Key: CONNECTORS-13 URL: https://issues.apache.org/jira/browse/CONNECTORS-13 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next The current implementation relies on the file system to synchronize activity between various LCF processes. This has several downsides: first, it is possible to get the file system into a state that is corrupted (by killing processes); second, this limits the future ability to spread crawler workload over multiple machines. It should be reasonably straightforward, and probably more resilient, to introduce a synchronization process, which all other LCF processes talk to in order to manage locks, shared data, and other synchronization activities. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-63) Add support for reports to API
[ https://issues.apache.org/jira/browse/CONNECTORS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-63: -- Description: The API does not currently have implemented support for any ManifoldCF reports. Add this functionality. was: The API does not currently have implemented support for any LCF reporting. Add this functionality. Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Add support for reports to API -- Key: CONNECTORS-63 URL: https://issues.apache.org/jira/browse/CONNECTORS-63 Project: ManifoldCF Issue Type: Improvement Components: API Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next The API does not currently have implemented support for any ManifoldCF reports. Add this functionality. -- 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: --- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next 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 Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Jack Krupansky Fix For: ManifoldCF next 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] [Updated] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-110: --- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB Key: CONNECTORS-110 URL: https://issues.apache.org/jira/browse/CONNECTORS-110 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next 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-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: --- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next 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 Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next 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-119) Submit patch requests for all remaining httpclient customizations
[ https://issues.apache.org/jira/browse/CONNECTORS-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-119: --- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Submit patch requests for all remaining httpclient customizations - Key: CONNECTORS-119 URL: https://issues.apache.org/jira/browse/CONNECTORS-119 Project: ManifoldCF Issue Type: Task Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next Now that commons-httpclient has accepted the NTLM patch, we can in theory start to use httpclient 4.x plain-vanilla as a replacement for our customized 3.1 httpclient. But first we should submit any remaining differences as patch requests. Specifically, the cross-path cookie allowance should be submitted. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-222) Would like support for building and running ManifoldCF under eclipse
[ https://issues.apache.org/jira/browse/CONNECTORS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-222: -- Assignee: Karl Wright Would like support for building and running ManifoldCF under eclipse Key: CONNECTORS-222 URL: https://issues.apache.org/jira/browse/CONNECTORS-222 Project: ManifoldCF Issue Type: New Feature Components: Framework agents process Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Being able to build and run under Eclipse would allow people to develop connectors and patches more readily. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-202) SOLR connector suport for commitWithin
[ https://issues.apache.org/jira/browse/CONNECTORS-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-202: --- Fix Version/s: ManifoldCF next 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 Fix For: ManifoldCF next 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-222) Would like support for building and running ManifoldCF under eclipse
[ https://issues.apache.org/jira/browse/CONNECTORS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095239#comment-13095239 ] Karl Wright commented on CONNECTORS-222: The maven support is now significant and probably counts as a resolution to this ticket. So I'm closing it. Would like support for building and running ManifoldCF under eclipse Key: CONNECTORS-222 URL: https://issues.apache.org/jira/browse/CONNECTORS-222 Project: ManifoldCF Issue Type: New Feature Components: Framework agents process Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Fix For: ManifoldCF 0.3 Being able to build and run under Eclipse would allow people to develop connectors and patches more readily. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-237) RSS Connector proxy code doesn't seem to function correctly
[ https://issues.apache.org/jira/browse/CONNECTORS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-237: --- Priority: Minor (was: Major) Fix Version/s: ManifoldCF next RSS Connector proxy code doesn't seem to function correctly --- Key: CONNECTORS-237 URL: https://issues.apache.org/jira/browse/CONNECTORS-237 Project: ManifoldCF Issue Type: Bug Components: RSS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Trying to crawl through a proxy fails. No activity is recorded but all fetches fail (with timeout errors) and are requeued. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-237) RSS Connector proxy code doesn't seem to function correctly
[ https://issues.apache.org/jira/browse/CONNECTORS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095241#comment-13095241 ] Karl Wright commented on CONNECTORS-237: This seems to be a problem only with certain proxies. Not quite sure what the criteria are for the problem occurring. But I've confirmed that crawling through most proxies still works. RSS Connector proxy code doesn't seem to function correctly --- Key: CONNECTORS-237 URL: https://issues.apache.org/jira/browse/CONNECTORS-237 Project: ManifoldCF Issue Type: Bug Components: RSS connector Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Fix For: ManifoldCF next Trying to crawl through a proxy fails. No activity is recorded but all fetches fail (with timeout errors) and are requeued. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-233) ManifoldCF would benefit from a generic push agent
[ https://issues.apache.org/jira/browse/CONNECTORS-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-233: --- Fix Version/s: ManifoldCF next ManifoldCF would benefit from a generic push agent -- Key: CONNECTORS-233 URL: https://issues.apache.org/jira/browse/CONNECTORS-233 Project: ManifoldCF Issue Type: New Feature Components: Framework agents process Affects Versions: ManifoldCF next Reporter: Karl Wright Fix For: ManifoldCF next ManifoldCF has a pull agent which crawls to get what it needs. There is, however, no push agents available. Developing a JSON-based push agent would demonstrate how to write one of these entities, and if done properly would also be useful in many off-the-shelf situations where notification is used. The most common model would involve an API to which change notifications could be reliably posted. A database table would maintain a list of the documents that needed processing, like the jobqueue. Fetching of documents would then need to be performed through a pluggable interface similar in some respects to IRepositoryConnector, but which would differ because version strings are unneeded. Indexing, of course, would proceed through the agents framework. I would anticipate that such an exercise would lead to some changes in the way the agents framework is structured. It is also possible to imagine that instead of a push agent, a notification service could be added to the pull-agent which would effectively do the same thing. Choosing the right approach would be part of this ticket. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-242) Connector support matrix page needs to be updated with both OpenSearchServer supported versions and CMIS supported versions
[ https://issues.apache.org/jira/browse/CONNECTORS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-242: --- Fix Version/s: ManifoldCF 0.3 Connector support matrix page needs to be updated with both OpenSearchServer supported versions and CMIS supported versions --- Key: CONNECTORS-242 URL: https://issues.apache.org/jira/browse/CONNECTORS-242 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Fix For: ManifoldCF 0.3 Connector support matrix page needs to be updated with both OpenSearchServer supported versions and CMIS supported versions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-34) eRoom authority and connector
[ https://issues.apache.org/jira/browse/CONNECTORS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-34: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next eRoom authority and connector - Key: CONNECTORS-34 URL: https://issues.apache.org/jira/browse/CONNECTORS-34 Project: ManifoldCF Issue Type: New Feature Components: eRoom connector Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Fix For: ManifoldCF next eRoom has a SOAP API which looks like it has enough power to perhaps implement a connector and an authority. The eRoom API url is here (and yes, it is a chinese url, but is legit): https://eroom.abraxas.ch/eroomHelp/en/API_Help/Api.htm#home_api.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-100) DB lock timeout, and/or indefinite or excessive database activity
[
https://issues.apache.org/jira/browse/CONNECTORS-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-100:
---
Affects Version/s: ManifoldCF 0.3
ManifoldCF 0.1
ManifoldCF 0.2
Fix Version/s: ManifoldCF next
DB lock timeout, and/or indefinite or excessive database activity
-
Key: CONNECTORS-100
URL: https://issues.apache.org/jira/browse/CONNECTORS-100
Project: ManifoldCF
Issue Type: Bug
Components: Framework core
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Environment: Running unmodified dist/example from trunk/ using the
default configuration.
Reporter: Andrzej Bialecki
Assignee: Karl Wright
Fix For: ManifoldCF next
When a job is started and running (via crawler-ui) occasionally it's not
possible to display a list of running jobs. The problem persists even after
restarting ACF. The following exception is thrown in the console:
{code}
org.apache.acf.core.interfaces.ACFException: Database exception: Exception
doing query: A lock could not be obtained within the time requested
at
org.apache.acf.core.database.Database.executeViaThread(Database.java:421)
at
org.apache.acf.core.database.Database.executeUncachedQuery(Database.java:465)
at
org.apache.acf.core.database.Database$QueryCacheExecutor.create(Database.java:1072)
at
org.apache.acf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144)
at
org.apache.acf.core.database.Database.executeQuery(Database.java:167)
at
org.apache.acf.core.database.DBInterfaceDerby.performQuery(DBInterfaceDerby.java:727)
at
org.apache.acf.crawler.jobs.JobManager.makeJobStatus(JobManager.java:5611)
at
org.apache.acf.crawler.jobs.JobManager.getAllStatus(JobManager.java:5549)
at
org.apache.jsp.showjobstatus_jsp._jspService(showjobstatus_jsp.java:316)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.sql.SQLTransactionRollbackException: A lock could not be
obtained within the time requested
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
at
[jira] [Updated] (CONNECTORS-94) fix common localization traps
[ https://issues.apache.org/jira/browse/CONNECTORS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-94: -- Affects Version/s: ManifoldCF 0.3 ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next fix common localization traps - Key: CONNECTORS-94 URL: https://issues.apache.org/jira/browse/CONNECTORS-94 Project: ManifoldCF Issue Type: Task Components: Framework core Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Robert Muir Assignee: Robert Muir Fix For: ManifoldCF next Searching thru the LCF code, i found several uses of the following that appear to be potentially dangerous: * getBytes() with no encoding: this is dangerous as the encoding is completely unspecified. In most places this should likely mean UTF-8 * getBytes(utf-8): this is mostly a nitpick, but this alias is not guaranteed to exist (see Charset docs). I suggest changing these all to UTF-8 * String.toLowerCase()/String.toUpperCase() with no specified Locale, where it appears the text is not used solely for display, but instead for 'caseless matching'. I suggest changing these to use either the root Locale: new Locale() or even easier, Locale.ENGLISH. This way ACF does not have surprising behavior on say a Turkish computer. I can contribute a patch to address these. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-241) OpenSearchServer connector needs how-to-build-and-deploy section
[ https://issues.apache.org/jira/browse/CONNECTORS-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095244#comment-13095244 ] Karl Wright commented on CONNECTORS-241: A patch was submitted under CONNECTORS-240, so I'm closing this ticket as a duplicate. OpenSearchServer connector needs how-to-build-and-deploy section Key: CONNECTORS-241 URL: https://issues.apache.org/jira/browse/CONNECTORS-241 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright The how-to-build-and-deploy page needs to be updated to include the OpenSearchServer connector info. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-248) File system crawl with HSQLDB aborts with a constraint error
[ https://issues.apache.org/jira/browse/CONNECTORS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-248: --- Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright File system crawl with HSQLDB aborts with a constraint error Key: CONNECTORS-248 URL: https://issues.apache.org/jira/browse/CONNECTORS-248 Project: ManifoldCF Issue Type: Bug Components: Framework agents process, Framework core Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 While running two jobs with overlapping files with HSQLDB, I got this error on the second job that aborted it: Error: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS The complete exception is here: ERROR 2011-08-31 21:07:06,029 (Worker thread '34') - Exception tossed: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS org.apache.manifoldcf.core.interfaces.ManifoldCFException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.reinterpretException(DBInterfaceHSQLDB.java:587) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performModification(DBInterfaceHSQLDB.java:607) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.performUpdate(DBInterfaceHSQLDB.java:242) at org.apache.manifoldcf.core.database.BaseTable.performUpdate(BaseTable.java:88) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.updateRowIds(IncrementalIngester.java:628) at org.apache.manifoldcf.agents.incrementalingest.IncrementalIngester.documentCheckMultiple(IncrementalIngester.java:588) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:653) Caused by: java.sql.SQLException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.jdbc.Util.sqlException(Util.java:255) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4659) at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(JDBCPreparedStatement.java:311) at org.apache.manifoldcf.core.database.Database.execute(Database.java:606) at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421) Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation; SYS_PK_10041 table: INGESTSTATUS at org.hsqldb.error.Error.error(Error.java:134) at org.hsqldb.Constraint.getException(Constraint.java:914) at org.hsqldb.index.IndexAVL.insert(IndexAVL.java:731) at org.hsqldb.persist.RowStoreAVL.indexRow(RowStoreAVL.java:171) at org.hsqldb.persist.RowStoreAVLDisk.indexRow(RowStoreAVLDisk.java:169) at org.hsqldb.TransactionManagerMVCC.addInsertAction(TransactionManagerMVCC.java:401) at org.hsqldb.Session.addInsertAction(Session.java:434) at org.hsqldb.Table.insertSingleRow(Table.java:2553) at org.hsqldb.StatementDML.update(StatementDML.java:1032) at org.hsqldb.StatementDML.executeUpdateStatement(StatementDML.java:541) at org.hsqldb.StatementDML.getResult(StatementDML.java:196) at org.hsqldb.StatementDMQL.execute(StatementDMQL.java:190) at org.hsqldb.Session.executeCompiledStatement(Session.java:1340) at org.hsqldb.Session.execute(Session.java:993) at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(JDBCPreparedStatement.java:4651) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-246) A file crawl exited with an unexpected jobqueue status error under HSQLDB
[ https://issues.apache.org/jira/browse/CONNECTORS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-246: --- Component/s: Framework core Affects Version/s: ManifoldCF 0.3 Fix Version/s: ManifoldCF 0.3 A file crawl exited with an unexpected jobqueue status error under HSQLDB --- Key: CONNECTORS-246 URL: https://issues.apache.org/jira/browse/CONNECTORS-246 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Under HSQLDB, a file crawl terminated with: Error: Unexpected jobqueue status - record id 1314721269570, expecting active status. The full trace was: ERROR 2011-08-30 12:23:48,962 (Worker thread '38') - Exception tossed: Unexpected jobqueue status - record id 1314721269570, expecting active status org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected jobqueue status - record id 1314721269570, expecting active status at org.apache.manifoldcf.crawler.jobs.JobQueue.updateCompletedRecord(JobQueue.java:633) at org.apache.manifoldcf.crawler.jobs.JobManager.markDocumentCompletedMultiple(JobManager.java:2386) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:798) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-240: --- Fix Version/s: ManifoldCF 0.3 OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Fix For: ManifoldCF 0.3 Attachments: oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-241) OpenSearchServer connector needs how-to-build-and-deploy section
[ https://issues.apache.org/jira/browse/CONNECTORS-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-241. Resolution: Duplicate Fix Version/s: ManifoldCF 0.3 See CONNECTORS-240. OpenSearchServer connector needs how-to-build-and-deploy section Key: CONNECTORS-241 URL: https://issues.apache.org/jira/browse/CONNECTORS-241 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Fix For: ManifoldCF 0.3 The how-to-build-and-deploy page needs to be updated to include the OpenSearchServer connector info. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-66) Document Active Directory authority configuration API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-66: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document Active Directory authority configuration API pieces Key: CONNECTORS-66 URL: https://issues.apache.org/jira/browse/CONNECTORS-66 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document Active Directory-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] [Updated] (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:all-tabpanel ] Karl Wright updated CONNECTORS-19: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next 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 Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next 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] [Updated] (CONNECTORS-75) Document Solr Connector configuration/specification API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-75: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document Solr Connector configuration/specification API pieces -- Key: CONNECTORS-75 URL: https://issues.apache.org/jira/browse/CONNECTORS-75 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document Solr 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] [Updated] (CONNECTORS-69) Document JDBC connector configuration/specification API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-69: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document JDBC connector configuration/specification API pieces -- Key: CONNECTORS-69 URL: https://issues.apache.org/jira/browse/CONNECTORS-69 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document JDBC 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] [Updated] (CONNECTORS-67) Document GTS output connector configuration/specification API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-67: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document GTS output connector configuration/specification API pieces Key: CONNECTORS-67 URL: https://issues.apache.org/jira/browse/CONNECTORS-67 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document GTS output 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] [Updated] (CONNECTORS-70) Document LiveLink configuration/specification/command API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-70: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document LiveLink configuration/specification/command API pieces Key: CONNECTORS-70 URL: https://issues.apache.org/jira/browse/CONNECTORS-70 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document LiveLink 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] [Updated] (CONNECTORS-64) Document the FileNet configuration/specification/command API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-64: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document the FileNet configuration/specification/command API pieces --- Key: CONNECTORS-64 URL: https://issues.apache.org/jira/browse/CONNECTORS-64 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document FileNet-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] [Updated] (CONNECTORS-68) Document jCIFS connector configuration/specification/command API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-68: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document jCIFS connector configuration/specification/command API pieces --- Key: CONNECTORS-68 URL: https://issues.apache.org/jira/browse/CONNECTORS-68 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document jCIFS 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] [Updated] (CONNECTORS-72) Document Meridio connector configuration/specification/command API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-72: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document Meridio connector configuration/specification/command API pieces - Key: CONNECTORS-72 URL: https://issues.apache.org/jira/browse/CONNECTORS-72 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document Meridio 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] [Updated] (CONNECTORS-141) Forrest skin files should be excluded from license check
[ https://issues.apache.org/jira/browse/CONNECTORS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-141: --- Affects Version/s: ManifoldCF 0.3 Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright Forrest skin files should be excluded from license check Key: CONNECTORS-141 URL: https://issues.apache.org/jira/browse/CONNECTORS-141 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 The following files are reported by RAT: [rat:report] Unapproved licenses: [rat:report] [rat:report] C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skins/common/xslt/html/split.xsl [rat:report] C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skins/lucene/note.txt [rat:report] [rat:report] *** According to Forrest developers, these files should simply be excluded by the license report. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-99) REST API serialization inconsistency
[
https://issues.apache.org/jira/browse/CONNECTORS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-99:
--
Affects Version/s: ManifoldCF 0.3
ManifoldCF 0.1
ManifoldCF 0.2
Fix Version/s: ManifoldCF next
REST API serialization inconsistency
Key: CONNECTORS-99
URL: https://issues.apache.org/jira/browse/CONNECTORS-99
Project: ManifoldCF
Issue Type: Wish
Components: API
Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
Environment: ACF trunk.
Reporter: Andrzej Bialecki
Priority: Minor
Fix For: ManifoldCF next
There is some inconsistency in REST APIs that makes the returned values more
difficult to process than necessary. It boils down to the fact that lists of
values are serialized into JSON arrays only when there is more than 1 element
on the list, but they are serialized into plain JSON objects when there is 0
or 1 element on the list. Example:
* listings of jobs, connectors, connections, repositories etc. all suffer
from this symptom:
{code}
* 1 element:
{job:{id:1283811504796,description:job 1 ...
* 2 elements:
{job:[{id:1283811504796,description:job 1 ...
{code}
* nested elements, such as e.g. job metadata:
{code}
1 element:
metadata:{_value_:,_attribute_name:jobKey1,_attribute_value:jobVal1}
2 elements:
metadata:[{_value_:,_attribute_name:jobKey1,_attribute_value:jobVal1},{_value_:,_attribute_name:jobKey2,_attribute_value:jobVal2}]
{code}
In my opinion, in all the above cases the API should always return a JSON
array for those elements that can occur with cardinality 1.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-144) Apache headers may not be necessary for README and DISCLAIMER
[ https://issues.apache.org/jira/browse/CONNECTORS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-144: --- Affects Version/s: ManifoldCF 0.3 Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright Apache headers may not be necessary for README and DISCLAIMER - Key: CONNECTORS-144 URL: https://issues.apache.org/jira/browse/CONNECTORS-144 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 One last comment is that the some of the doc files like the README and DISCLAIMER have the Apache License header which i don't think is necessary and the README is the first thing people look at so having a big glob of legal text right at the top isn't so attractive. We'd need to check if this is indeed true. For the DISCLAIMER it may well be true, not sure about the README. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-65) Document File Connector configuration/specification/command API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-65: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document File Connector configuration/specification/command API pieces -- Key: CONNECTORS-65 URL: https://issues.apache.org/jira/browse/CONNECTORS-65 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document File System 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] [Updated] (CONNECTORS-73) Document RSS connector configuration/specification API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-73: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document RSS connector configuration/specification API pieces - Key: CONNECTORS-73 URL: https://issues.apache.org/jira/browse/CONNECTORS-73 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document RSS 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] [Updated] (CONNECTORS-74) Document SharePoint connector configuration/specification/command API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-74: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document SharePoint connector configuration/specification/command API pieces Key: CONNECTORS-74 URL: https://issues.apache.org/jira/browse/CONNECTORS-74 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document SharePoint 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] [Updated] (CONNECTORS-76) Document Web Connector configuration/specification API pieces
[ https://issues.apache.org/jira/browse/CONNECTORS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-76: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next Document Web Connector configuration/specification API pieces - Key: CONNECTORS-76 URL: https://issues.apache.org/jira/browse/CONNECTORS-76 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next Need to document web 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] [Updated] (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:all-tabpanel ] Karl Wright updated CONNECTORS-27: -- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next 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 Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Ralph Benjamin Ruijs Priority: Minor Fix For: ManifoldCF next 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-176) It might be nice to have a direct link from the site navigation area to the performance tuning page
[ https://issues.apache.org/jira/browse/CONNECTORS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-176: --- Fix Version/s: ManifoldCF 0.3 It might be nice to have a direct link from the site navigation area to the performance tuning page --- Key: CONNECTORS-176 URL: https://issues.apache.org/jira/browse/CONNECTORS-176 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 The only way to get to the performance tuning page now is through the developer support page. A direct link might make it easier. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-178) Implement ability to run ManifoldCF with Derby in multiprocess mode
[ https://issues.apache.org/jira/browse/CONNECTORS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-178: --- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next 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 Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next 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] [Updated] (CONNECTORS-180) Connector factories all have a Pool class that should be derived from a base Pool class
[ https://issues.apache.org/jira/browse/CONNECTORS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-180: --- Affects Version/s: ManifoldCF 0.1 ManifoldCF 0.2 Fix Version/s: ManifoldCF next 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 Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2 Reporter: Karl Wright Assignee: Erlend Garåsen Priority: Minor Fix For: ManifoldCF next 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] [Updated] (CONNECTORS-177) File System Connector has some testing code in it
[ https://issues.apache.org/jira/browse/CONNECTORS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-177: --- Fix Version/s: ManifoldCF 0.3 Assignee: Karl Wright 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 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 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-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: --- Fix Version/s: ManifoldCF next 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 0.3 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF next 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] [Commented] (CONNECTORS-207) ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead
[ https://issues.apache.org/jira/browse/CONNECTORS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095247#comment-13095247 ] Karl Wright commented on CONNECTORS-207: This has been resolved through the use of ServiceInterruption exceptions rather than the REPOSITORY_CONNECTION_ERROR ManifoldCFException type. ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead -- Key: CONNECTORS-207 URL: https://issues.apache.org/jira/browse/CONNECTORS-207 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 The way a worker thread treats ManifoldCFException type REPOSITORY_CONNECTION_ERROR is to wait 5 minutes and retry. It might want to just allow the job to be aborted with no retries. The current behavior is not actually *wrong*, but the circumstances under which it was added were the result of severe problems at various sites that were unrelated to ManifoldCF. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-207) ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead
[ https://issues.apache.org/jira/browse/CONNECTORS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-207. Resolution: Duplicate Fix Version/s: ManifoldCF 0.3 ManifoldCFException type REPOSITORY_CONNECTION_ERROR causes a five-minute retry, but may want to abort the job instead -- Key: CONNECTORS-207 URL: https://issues.apache.org/jira/browse/CONNECTORS-207 Project: ManifoldCF Issue Type: Bug Components: Framework crawler agent Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 The way a worker thread treats ManifoldCFException type REPOSITORY_CONNECTION_ERROR is to wait 5 minutes and retry. It might want to just allow the job to be aborted with no retries. The current behavior is not actually *wrong*, but the circumstances under which it was added were the result of severe problems at various sites that were unrelated to ManifoldCF. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-247) Need a set of tests for the scripting language client
[ https://issues.apache.org/jira/browse/CONNECTORS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-247: --- Fix Version/s: ManifoldCF 0.3 Need a set of tests for the scripting language client - Key: CONNECTORS-247 URL: https://issues.apache.org/jira/browse/CONNECTORS-247 Project: ManifoldCF Issue Type: Test Components: Tests Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 We need unit tests for the script language client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-141) Forrest skin files should be excluded from license check
[ https://issues.apache.org/jira/browse/CONNECTORS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-141. Resolution: Fixed r1164084. Forrest skin files should be excluded from license check Key: CONNECTORS-141 URL: https://issues.apache.org/jira/browse/CONNECTORS-141 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 The following files are reported by RAT: [rat:report] Unapproved licenses: [rat:report] [rat:report] C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skins/common/xslt/html/split.xsl [rat:report] C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skins/lucene/note.txt [rat:report] [rat:report] *** According to Forrest developers, these files should simply be excluded by the license report. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-144) Apache headers may not be necessary for README and DISCLAIMER
[ https://issues.apache.org/jira/browse/CONNECTORS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-144. Resolution: Fixed r1164086. Apache headers may not be necessary for README and DISCLAIMER - Key: CONNECTORS-144 URL: https://issues.apache.org/jira/browse/CONNECTORS-144 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.3 One last comment is that the some of the doc files like the README and DISCLAIMER have the Apache License header which i don't think is necessary and the README is the first thing people look at so having a big glob of legal text right at the top isn't so attractive. We'd need to check if this is indeed true. For the DISCLAIMER it may well be true, not sure about the README. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-242) Connector support matrix page needs to be updated with both OpenSearchServer supported versions and CMIS supported versions
[ https://issues.apache.org/jira/browse/CONNECTORS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-242. --- Resolution: Fixed r1164091 Connector support matrix page needs to be updated with both OpenSearchServer supported versions and CMIS supported versions --- Key: CONNECTORS-242 URL: https://issues.apache.org/jira/browse/CONNECTORS-242 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.3 Connector support matrix page needs to be updated with both OpenSearchServer supported versions and CMIS supported versions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-240: -- Assignee: Karl Wright OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Incubator PMC/Board report for September 2011 (connectors-dev@incubator.apache.org)
Here's a report proposal: ManifoldCF --Description-- ManifoldCF is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of repository connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio (Autonomy), SharePoint (Microsoft), JDBC, CIFS file systems, CMIS repositories, RSS feeds, and web content. Output support includes Solr, MetaCarta GTS, and OpenSearchServer. ManifoldCF also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results. ManifoldCF has been in incubation since January, 2010. It was originally a planned subproject of Lucene but is now a likely top-level project. --A list of the three most important issues to address in the move towards graduation-- 1. We need at least one additional active committer, as well as additional users and repeat contributors 2. We want to finish the current release before graduating 3. We'd like to see long-term contributions for project testing, especially infrastructure access --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?-- All issues have been addressed to our satisfaction at this time. --How has the community developed since the last report?-- A book has been completed, and is now available in early-release form, available from Manning Publishing, at http://www.manning.com/wright. We have signed up a new committer in this quarter and are discussing a second. One of our mentors (Grant Ingersoll) resigned. We continue to have user community interest. We are participating this year in both Apache Eurocon and Apache North America. We've had a number of extremely helpful contributions from the field, including the CMIS connector and the OpenSearchServer output connector. We have started to discuss graduation from the incubator, which may come to pass by the end of the year. --How has the project developed since the last report?-- An 0.1 release was made on January 31, 2011, and a 0.2 release occurred on May 17, 2011. Another release is scheduled for September 15, 2011, and will contain significant new features, including two new connectors and a client scripting language. Signed off by mentor: On Thu, Sep 1, 2011 at 10:00 AM, no-re...@apache.org wrote: Dear ManifoldCF Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 September 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/September2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for September 2011 (connectors-dev@incubator.apache.org)
nice one Karl :) Tommaso 2011/9/1 Karl Wright daddy...@gmail.com Here's a report proposal: ManifoldCF --Description-- ManifoldCF is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of repository connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio (Autonomy), SharePoint (Microsoft), JDBC, CIFS file systems, CMIS repositories, RSS feeds, and web content. Output support includes Solr, MetaCarta GTS, and OpenSearchServer. ManifoldCF also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results. ManifoldCF has been in incubation since January, 2010. It was originally a planned subproject of Lucene but is now a likely top-level project. --A list of the three most important issues to address in the move towards graduation-- 1. We need at least one additional active committer, as well as additional users and repeat contributors 2. We want to finish the current release before graduating 3. We'd like to see long-term contributions for project testing, especially infrastructure access --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?-- All issues have been addressed to our satisfaction at this time. --How has the community developed since the last report?-- A book has been completed, and is now available in early-release form, available from Manning Publishing, at http://www.manning.com/wright. We have signed up a new committer in this quarter and are discussing a second. One of our mentors (Grant Ingersoll) resigned. We continue to have user community interest. We are participating this year in both Apache Eurocon and Apache North America. We've had a number of extremely helpful contributions from the field, including the CMIS connector and the OpenSearchServer output connector. We have started to discuss graduation from the incubator, which may come to pass by the end of the year. --How has the project developed since the last report?-- An 0.1 release was made on January 31, 2011, and a 0.2 release occurred on May 17, 2011. Another release is scheduled for September 15, 2011, and will contain significant new features, including two new connectors and a client scripting language. Signed off by mentor: On Thu, Sep 1, 2011 at 10:00 AM, no-re...@apache.org wrote: Dear ManifoldCF Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 September 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/September2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for September 2011 (connectors-dev@incubator.apache.org)
I pasted it into the wiki - please feel free to modify or add or sign off. Karl On Thu, Sep 1, 2011 at 11:43 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: nice one Karl :) Tommaso 2011/9/1 Karl Wright daddy...@gmail.com Here's a report proposal: ManifoldCF --Description-- ManifoldCF is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of repository connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio (Autonomy), SharePoint (Microsoft), JDBC, CIFS file systems, CMIS repositories, RSS feeds, and web content. Output support includes Solr, MetaCarta GTS, and OpenSearchServer. ManifoldCF also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results. ManifoldCF has been in incubation since January, 2010. It was originally a planned subproject of Lucene but is now a likely top-level project. --A list of the three most important issues to address in the move towards graduation-- 1. We need at least one additional active committer, as well as additional users and repeat contributors 2. We want to finish the current release before graduating 3. We'd like to see long-term contributions for project testing, especially infrastructure access --Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?-- All issues have been addressed to our satisfaction at this time. --How has the community developed since the last report?-- A book has been completed, and is now available in early-release form, available from Manning Publishing, at http://www.manning.com/wright. We have signed up a new committer in this quarter and are discussing a second. One of our mentors (Grant Ingersoll) resigned. We continue to have user community interest. We are participating this year in both Apache Eurocon and Apache North America. We've had a number of extremely helpful contributions from the field, including the CMIS connector and the OpenSearchServer output connector. We have started to discuss graduation from the incubator, which may come to pass by the end of the year. --How has the project developed since the last report?-- An 0.1 release was made on January 31, 2011, and a 0.2 release occurred on May 17, 2011. Another release is scheduled for September 15, 2011, and will contain significant new features, including two new connectors and a client scripting language. Signed off by mentor: On Thu, Sep 1, 2011 at 10:00 AM, no-re...@apache.org wrote: Dear ManifoldCF Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 September 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/September2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
