[jira] [Comment Edited] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
[ https://issues.apache.org/jira/browse/CONNECTORS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773001#comment-17773001 ] Mingchun Zhao edited comment on CONNECTORS-1748 at 10/11/23 7:56 PM: - Hi [~daddywri] , I've prepared a PR as below: https://github.com/apache/manifoldcf/pull/154 Could you confirm this please? Best regards, Mingchun was (Author: mingchun.zhao): Hi [~daddywri] , I've prepared a PR as below: [https://github.com/apache/manifoldcf/pull/153] Could you confirm this please? Best regards, Mingchun > Add "User-Agent platform" option for crawling mobile websites > - > > Key: CONNECTORS-1748 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Mingchun Zhao >Priority: Major > > Hi [~daddywri] , > Allow me propose a new feature for crawling mobile sites which restrict > access to content based on User-Agent header. > Actually, Our customer's mobile website was failing to crawl because access > was restricted based on whether the User-Agent request header includes the > mobile info. For this reason, we added the "User-Agent platform" option to > the new "Request Headers" tab on the web repository connector page so that > this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
[ https://issues.apache.org/jira/browse/CONNECTORS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao reassigned CONNECTORS-1748: - Assignee: (was: Mingchun Zhao) > Add "User-Agent platform" option for crawling mobile websites > - > > Key: CONNECTORS-1748 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Mingchun Zhao >Priority: Major > > Hi [~daddywri] , > Allow me propose a new feature for crawling mobile sites which restrict > access to content based on User-Agent header. > Actually, Our customer's mobile website was failing to crawl because access > was restricted based on whether the User-Agent request header includes the > mobile info. For this reason, we added the "User-Agent platform" option to > the new "Request Headers" tab on the web repository connector page so that > this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
[ https://issues.apache.org/jira/browse/CONNECTORS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773001#comment-17773001 ] Mingchun Zhao commented on CONNECTORS-1748: --- Hi [~daddywri] , I've prepared a PR as below: [https://github.com/apache/manifoldcf/pull/153] Could you confirm this please? Best regards, Mingchun > Add "User-Agent platform" option for crawling mobile websites > - > > Key: CONNECTORS-1748 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Mingchun Zhao >Assignee: Mingchun Zhao >Priority: Major > > Hi [~daddywri] , > Allow me propose a new feature for crawling mobile sites which restrict > access to content based on User-Agent header. > Actually, Our customer's mobile website was failing to crawl because access > was restricted based on whether the User-Agent request header includes the > mobile info. For this reason, we added the "User-Agent platform" option to > the new "Request Headers" tab on the web repository connector page so that > this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1748) Add "User-Agent platform" option for crawling mobile websites
Mingchun Zhao created CONNECTORS-1748: - Summary: Add "User-Agent platform" option for crawling mobile websites Key: CONNECTORS-1748 URL: https://issues.apache.org/jira/browse/CONNECTORS-1748 Project: ManifoldCF Issue Type: New Feature Reporter: Mingchun Zhao Assignee: Mingchun Zhao Hi [~daddywri] , Allow me propose a new feature for crawling mobile sites which restrict access to content based on User-Agent header. Actually, Our customer's mobile website was failing to crawl because access was restricted based on whether the User-Agent request header includes the mobile info. For this reason, we added the "User-Agent platform" option to the new "Request Headers" tab on the web repository connector page so that this mobile website doesn't fail to crawl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729126#comment-17729126 ] Mingchun Zhao commented on CONNECTORS-1740: --- Hi [~kwri...@metacarta.com] [~julienFL] , I’ve tried to modified the source code for using Zookeeper `3.5.6` and migrating Java from 8 to `11`, and the test run-tests-framework was OK. Attached the patch [^CONNECTORS-1740.patch] I used in my test. Also, I tried various other Zookeeper versions(3.6.2, 3.7.0, 3.7.2, 3.8.0, 3.8.1), but all of them failed in the test run-tests-framework due to an error as below. ``` [junit] [reader] INFO org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=localhost:8348 sessionTimeout=2000 watcher=org.apache.manifoldcf.core.lockmanager.ZooKeeperConnection$ZooKeeperWatcher@b647be3 [junit] [reader] INFO org.apache.zookeeper.ClientCnxnSocket - jute.maxbuffer value is 1048575 Bytes [junit] [reader] INFO org.apache.zookeeper.ClientCnxn - zookeeper.request.timeout value is 0. feature enabled=false [junit] [reader-SendThread(localhost:8348)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server localhost/0:0:0:0:0:0:0:1:8348. [junit] [reader-SendThread(localhost:8348)] INFO org.apache.zookeeper.ClientCnxn - SASL config status: Will not attempt to authenticate using SASL (unknown error) [junit] [reader-SendThread(localhost:8348)] WARN org.apache.zookeeper.ClientCnxn - Session 0x0 for sever localhost/0:0:0:0:0:0:0:1:8348, Closing socket connection. Attempting reconnect except it is a SessionExpiredException. [junit] java.net.ConnectException: Connection refused [junit] at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:344) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1280) ``` > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1740: -- Attachment: CONNECTORS-1740.patch > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726850#comment-17726850 ] Mingchun Zhao commented on CONNECTORS-1747: --- [~kwri...@metacarta.com] Thanks, that's so helpful! > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > Fix For: ManifoldCF 2.25 > > Attachments: CONNECTORS-1747.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726777#comment-17726777 ] Mingchun Zhao commented on CONNECTORS-1747: --- [~kwri...@metacarta.com], If you need my help with the release work, I'll do whatever I can, so feel free to ask me please. I feel sorry for not being able to participate in ManifoldCF community activities until now, but I will be actively involved in MCF activities from now on. Also, I will try to contact committers in Japan to liven up ManifoldCF together. Thank you. > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > Fix For: ManifoldCF 2.25 > > Attachments: CONNECTORS-1747.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725971#comment-17725971 ] Mingchun Zhao commented on CONNECTORS-1747: --- Hi [~kwri...@metacarta.com], Thank you for confirming this patch. BTW, do we have a plan for when the next release of ManifoldCF will be? The project I'm participating in now uses ManifoldCF+PostgreSQL and will be released at the end of next month. It would be very helpful if the latest version of MCF could be used. If there is anything I can do, I will actively participate in the MCF release work. Kind regards, Mingchun > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > Attachments: CONNECTORS-1747.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725478#comment-17725478 ] Mingchun Zhao commented on CONNECTORS-1747: --- Hi [~kwri...@metacarta.com], I've created a patch as you mentioned above, could you please confirm the attached [^CONNECTORS-1747.patch] In my testing with the attached patch, when I set the additional property as below, `` I confirmed: (1) The hopcount handling was completely disabled. (2) No records were inserted into the `intrinsiclink` or `hopcount` tables. (3) The hopcount tab did not appear in the UI for any job. Regards, Mingchun > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > Attachments: CONNECTORS-1747.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1747: -- Attachment: CONNECTORS-1747.patch > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > Attachments: CONNECTORS-1747.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1747: -- Attachment: (was: JobManager.java.patch) > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724663#comment-17724663 ] Mingchun Zhao commented on CONNECTORS-1747: --- [~kwri...@metacarta.com] Thank you for your review, it was very helpful. I understood, will try and fix the patch as you mentioned above. > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1747: -- Attachment: JobManager.java.patch > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1747: -- Attachment: (was: JobManager.java.patch) > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1747: -- Attachment: JobManager.java.patch > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723328#comment-17723328 ] Mingchun Zhao edited comment on CONNECTORS-1747 at 5/17/23 3:18 AM: Hello, I changed spec for new property as below. Could you please review the attached new patch? You can use this property to disable logging hopcount to database only for jobs with hopcount mode "keep unreachable documents, forever" specified in the "Hop Filters" tab. was (Author: mingchun.zhao): Hello, I changed spec for new property as below. Could you please review the attached new patch [^JobManager.java.patch2]? You can use this property to disable logging hopcount to database only for jobs with hopcount mode "keep unreachable documents, forever" specified in the "Hop Filters" tab. > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1747: -- Attachment: (was: JobManager.java.patch) > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723328#comment-17723328 ] Mingchun Zhao commented on CONNECTORS-1747: --- Hello, I changed spec for new property as below. Could you please review the attached new patch [^JobManager.java.patch2]? You can use this property to disable logging hopcount to database only for jobs with hopcount mode "keep unreachable documents, forever" specified in the "Hop Filters" tab. > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722975#comment-17722975 ] Mingchun Zhao commented on CONNECTORS-1747: --- Hello, If there are no objections to the above patch, would it be okay to commit it in a couple of days? > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722789#comment-17722789 ] Mingchun Zhao commented on CONNECTORS-1747: --- Hello, I’ve tried to create a patch for adding the below property to disable logging hopcount to the database as below. "org.apache.manifoldcf.db.postgres.crewler.jobs.store_hopcount" If you do not require hopcount from within, this will disable logging hotcount to the related database tables. This can increase throughput and reduce the rate of growth of the database. defaults to true(logging hopcount to the database). In my testing with the attached patch, I compared the execution time of the same job with the property “store_hopcount” set to true and false. As a result, the throughput doubled and the rate of growth of the database was cut by more than half, while the number of crawled documents remained the same. [^JobManager.java.patch] > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1747) Add a property to disable logging hop count to database
[ https://issues.apache.org/jira/browse/CONNECTORS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1747: -- Attachment: JobManager.java.patch > Add a property to disable logging hop count to database > --- > > Key: CONNECTORS-1747 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 > Project: ManifoldCF > Issue Type: Improvement >Reporter: Mingchun Zhao >Priority: Major > Attachments: JobManager.java.patch > > > If we do not require “Hop Filters“ feature, we need to consider to disable > logging records related to hopcount to database like "intrinsiclink" and > "hopcount" tables. This can increase throughput and reduce the rate of growth > of the database. > I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1747) Add a property to disable logging hop count to database
Mingchun Zhao created CONNECTORS-1747: - Summary: Add a property to disable logging hop count to database Key: CONNECTORS-1747 URL: https://issues.apache.org/jira/browse/CONNECTORS-1747 Project: ManifoldCF Issue Type: Improvement Reporter: Mingchun Zhao If we do not require “Hop Filters“ feature, we need to consider to disable logging records related to hopcount to database like "intrinsiclink" and "hopcount" tables. This can increase throughput and reduce the rate of growth of the database. I will try to create a patch for this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722207#comment-17722207 ] Mingchun Zhao edited comment on CONNECTORS-1746 at 5/12/23 10:34 PM: - Hello, Here is a patch for adding options for PostgreSQL’s “ANALYZE” command. I’ve tried to add two properties to handle 'ANALYZE' command as below. 1. "org.apache.manifoldcf.db.postgres.analyzeatstart" If this property is set to true, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." at the start of job. defaults to false (not to run "ANALYZE" at the start). 2. "org.apache.manifoldcf.db.postgres.analyzeratethreshold" If this property is set to a positive integer, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." only when events per second drops below the threshold. defaults to 0(not to check event rate). I tested using the attached patch and confirmed that the “ANALYZE” command was executed correctly in the above two situations. Especially, when MCF's throughput (event counts per second) dropped due to PostgreSQL's bad query plan, an “ANALYZE” command was executed and the MCF's performance recovered. [^DBInterfacePostgreSQL.java.patch] was (Author: mingchun.zhao): Hello, Here is a patch for adding options for PostgreSQL’s “ANALYZE” command. I’ve tried to add two properties to handle 'ANALYZE' command as below. 1. "org.apache.manifoldcf.db.postgres.analyzeatstart" If this property is set to true, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." at the start of job. defaults to false (not to run "ANALYZE" at the start). 2. "org.apache.manifoldcf.db.postgres.analyzeratethreshold" If this property is set to a positive integer, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." only when events per second drops below the threshold. defaults to 1 (1 event processed per second). I tested using the attached patch and confirmed that the “ANALYZE” command was executed correctly in the above two situations. Especially, when MCF's throughput (event counts per second) dropped due to PostgreSQL's bad query plan, an “ANALYZE” command was executed and the MCF's performance recovered. [^DBInterfacePostgreSQL.java.patch] > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Assignee: Karl Wright >Priority: Major > Attachments: DBInterfacePostgreSQL.java.patch > > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > 'org.apache.manifoldcf.db.postgres.analyze.', it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722207#comment-17722207 ] Mingchun Zhao edited comment on CONNECTORS-1746 at 5/12/23 3:25 PM: Hello, Here is a patch for adding options for PostgreSQL’s “ANALYZE” command. I’ve tried to add two properties to handle 'ANALYZE' command as below. 1. "org.apache.manifoldcf.db.postgres.analyzeatstart" If this property is set to true, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." at the start of job. defaults to false (not to run "ANALYZE" at the start). 2. "org.apache.manifoldcf.db.postgres.analyzeratethreshold" If this property is set to a positive integer, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." only when events per second drops below the threshold. defaults to 1 (1 event processed per second). I tested using the attached patch and confirmed that the “ANALYZE” command was executed correctly in the above two situations. Especially, when MCF's throughput (event counts per second) dropped due to PostgreSQL's bad query plan, an “ANALYZE” command was executed and the MCF's performance recovered. [^DBInterfacePostgreSQL.java.patch] was (Author: mingchun.zhao): Hello, Here is a patch for adding options for PostgreSQL’s “ANALYZE” command. I’ve tried to add two properties to handle 'ANALYZE' command as below. # "org.apache.manifoldcf.db.postgres.analyzeatstart" If this property is set to true, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." at the start of job. defaults to false (not to run "ANALYZE" at the start). # "org.apache.manifoldcf.db.postgres.analyzeratethreshold" If this property is set to a positive integer, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." only when events per second drops below the threshold. defaults to 1 (1 event processed per second). I tested using the attached patch and confirmed that the “ANALYZE” command was executed correctly in the above two situations. Especially, when MCF's throughput (event counts per second) dropped due to PostgreSQL's bad query plan, an “ANALYZE” command was executed and the MCF's performance recovered. [^DBInterfacePostgreSQL.java.patch] > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > Attachments: DBInterfacePostgreSQL.java.patch > > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > 'org.apache.manifoldcf.db.postgres.analyze.', it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722207#comment-17722207 ] Mingchun Zhao commented on CONNECTORS-1746: --- Hello, Here is a patch for adding options for PostgreSQL’s “ANALYZE” command. I’ve tried to add two properties to handle 'ANALYZE' command as below. # "org.apache.manifoldcf.db.postgres.analyzeatstart" If this property is set to true, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." at the start of job. defaults to false (not to run "ANALYZE" at the start). # "org.apache.manifoldcf.db.postgres.analyzeratethreshold" If this property is set to a positive integer, then analyze a table which is specified by property "org.apache.manifoldcf.db.postgres.analyze." only when events per second drops below the threshold. defaults to 1 (1 event processed per second). I tested using the attached patch and confirmed that the “ANALYZE” command was executed correctly in the above two situations. Especially, when MCF's throughput (event counts per second) dropped due to PostgreSQL's bad query plan, an “ANALYZE” command was executed and the MCF's performance recovered. [^DBInterfacePostgreSQL.java.patch] > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > Attachments: DBInterfacePostgreSQL.java.patch > > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > 'org.apache.manifoldcf.db.postgres.analyze.', it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1746: -- Attachment: DBInterfacePostgreSQL.java.patch > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > Attachments: DBInterfacePostgreSQL.java.patch > > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > 'org.apache.manifoldcf.db.postgres.analyze.', it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1746: -- Description: Sometimes, the crawling does not process any documents for a while and there is nothing logged about long-running queries. The performance can be restored by firing the 'ANALYZE' command manually. It seems that a bad query plan caused this performance problem. Therefore, in addition to the current configuration parameter 'org.apache.manifoldcf.db.postgres.analyze.', it is considered necessary to execute the 'ANALYZE' even in the following situations. 1. When the number of records in the table exceeds the number required for creating a execution plan after the job starts. 2. When the crawling performance slows down. For example, if the processing rate of documents drops below a specified threshold. was: Sometimes, the crawling does not process any documents for a while and there is nothing logged about long-running queries. The performance can be restored by firing the 'ANALYZE' command manually. It seems that a bad query plan caused this performance problem. Therefore, in addition to the current configuration parameter 'org.apache.manifoldcf.db.postgres.analyze.', it is considered necessary to execute the 'ANALYZE' even in the following situations. 1. When the number of records in the table exceeds the number required for creating a execution plan after the job starts. 2. When the crawling performance slows down. For example, if the processing rate of documents drops below a specified threshold. So, how about adding two parameters to handle the timing of 'ANALYZE' execution as below? 1.'org.apache.manifoldcf.db.postgres.analyze..minimumrowcount' Specify how many records should be inserted before carrying out an 'ANALYZE' on the specified table as the first time.defaults to 100. 2.'org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate' Specify the minimum number of documents processed per minute. If the processing rate of documents drops below this threshold, the 'ANALYZE' will be executed. defaults to 1. > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > 'org.apache.manifoldcf.db.postgres.analyze.', it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1746: -- Description: Sometimes, the crawling does not process any documents for a while and there is nothing logged about long-running queries. The performance can be restored by firing the 'ANALYZE' command manually. It seems that a bad query plan caused this performance problem. Therefore, in addition to the current configuration parameter 'org.apache.manifoldcf.db.postgres.analyze.', it is considered necessary to execute the 'ANALYZE' even in the following situations. 1. When the number of records in the table exceeds the number required for creating a execution plan after the job starts. 2. When the crawling performance slows down. For example, if the processing rate of documents drops below a specified threshold. So, how about adding two parameters to handle the timing of 'ANALYZE' execution as below? 1.'org.apache.manifoldcf.db.postgres.analyze..minimumrowcount' Specify how many records should be inserted before carrying out an 'ANALYZE' on the specified table as the first time.defaults to 100. 2.'org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate' Specify the minimum number of documents processed per minute. If the processing rate of documents drops below this threshold, the 'ANALYZE' will be executed. defaults to 1. was: Sometimes, the crawling does not process any documents for a while and there is nothing logged about long-running queries. The performance can be restored by firing the 'ANALYZE' command manually. It seems that a bad query plan caused this performance problem. Therefore, in addition to the current configuration parameter org.apache.manifoldcf.db.postgres.analyze. , it is considered necessary to execute the 'ANALYZE' even in the following situations. 1. When the number of records in the table exceeds the number required for creating a execution plan after the job starts. 2. When the crawling performance slows down. For example, if the processing rate of documents drops below a specified threshold. So, how about adding two parameters to handle the timing of 'ANALYZE' execution as below? 1. `org.apache.manifoldcf.db.postgres.analyze..minimumrowcount` Specify how many records should be inserted before carrying out an 'ANALYZE' on the specified table as the first time.defaults to 100. 2.`org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate` Specify the number of documents processed in the last minute. If the actual processing rate falls below this, the 'ANALYZE' will be executed. defaults to 1. > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > 'org.apache.manifoldcf.db.postgres.analyze.', it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. > So, how about adding two parameters to handle the timing of 'ANALYZE' > execution as below? > 1.'org.apache.manifoldcf.db.postgres.analyze..minimumrowcount' > Specify how many records should be inserted before carrying out an 'ANALYZE' > on the specified table as the first time.defaults to 100. > 2.'org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate' > Specify the minimum number of documents processed per minute. If the > processing rate of documents drops below this threshold, the 'ANALYZE' will > be executed. defaults to 1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1746: -- Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the database. (was: I am using ManifoldCF 2.24 with PostgreSQL 12.14 as the database. ) > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: Using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > org.apache.manifoldcf.db.postgres.analyze. , it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. > So, how about adding two parameters to handle the timing of 'ANALYZE' > execution as below? > 1. `org.apache.manifoldcf.db.postgres.analyze..minimumrowcount` > Specify how many records should be inserted before carrying out an 'ANALYZE' > on the specified table as the first time.defaults to 100. > 2.`org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate` > Specify the number of documents processed in the last minute. If the actual > processing rate falls below this, the 'ANALYZE' will be executed. defaults to > 1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1746: -- Description: Sometimes, the crawling does not process any documents for a while and there is nothing logged about long-running queries. The performance can be restored by firing the 'ANALYZE' command manually. It seems that a bad query plan caused this performance problem. Therefore, in addition to the current configuration parameter org.apache.manifoldcf.db.postgres.analyze. , it is considered necessary to execute the 'ANALYZE' even in the following situations. 1. When the number of records in the table exceeds the number required for creating a execution plan after the job starts. 2. When the crawling performance slows down. For example, if the processing rate of documents drops below a specified threshold. So, how about adding two parameters to handle the timing of 'ANALYZE' execution as below? 1. `org.apache.manifoldcf.db.postgres.analyze..minimumrowcount` Specify how many records should be inserted before carrying out an 'ANALYZE' on the specified table as the first time.defaults to 100. 2.`org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate` Specify the number of documents processed in the last minute. If the actual processing rate falls below this, the 'ANALYZE' will be executed. defaults to 1. was: Sometimes, the crawling does not process any documents for a while and there is nothing logged about long-running queries. The performance can be restored by firing the 'ANALYZE' command manually. It seems that a bad query plan caused this performance problem. Therefore, in addition to the current configuration parameter org.apache.manifoldcf.db.postgres.analyze. , it is considered necessary to execute the 'ANALYZE' even in the following situations. 1. When the number of records in the table exceeds the number required for creating an query plan after the job starts. 2. When the crawling performance slows down. For example, if the document processing rate drops below a specified threshold. How about adding two parameters to handle the timing of 'ANALYZE' execution as below? 1. `org.apache.manifoldcf.db.postgres.analyze..minimumrowcount` Specify how many records should be accumulated before carrying out an 'ANALYZE' on the specified table as the first time.defaults to 100. 2.`org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate` Specify the number of documents processed in the last minute. If the actual processing rate falls below this, the 'ANALYZE' will be carrying out. defaults to 1. > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: I am using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > org.apache.manifoldcf.db.postgres.analyze. , it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating a execution plan after the job starts. > 2. When the crawling performance slows down. For example, if the processing > rate of documents drops below a specified threshold. > So, how about adding two parameters to handle the timing of 'ANALYZE' > execution as below? > 1. `org.apache.manifoldcf.db.postgres.analyze..minimumrowcount` > Specify how many records should be inserted before carrying out an 'ANALYZE' > on the specified table as the first time.defaults to 100. > 2.`org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate` > Specify the number of documents processed in the last minute. If the actual > processing rate falls below this, the 'ANALYZE' will be executed. defaults to > 1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1746) Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
[ https://issues.apache.org/jira/browse/CONNECTORS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-1746: -- Summary: Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling become extremely slow. (was: Adding execution conditions of PostgreSQL's ANALYZE command to avoid crawling become extremely slow.) > Adding conditions to execute PostgreSQL's ANALYZE command to avoid crawling > become extremely slow. > -- > > Key: CONNECTORS-1746 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector > Environment: I am using ManifoldCF 2.24 with PostgreSQL 12.14 as the > database. >Reporter: Mingchun Zhao >Priority: Major > > Sometimes, the crawling does not process any documents for a while and there > is nothing logged about long-running queries. The performance can be restored > by firing the 'ANALYZE' command manually. It seems that a bad query plan > caused this performance problem. > Therefore, in addition to the current configuration parameter > org.apache.manifoldcf.db.postgres.analyze. , it is considered > necessary to execute the 'ANALYZE' even in the following situations. > 1. When the number of records in the table exceeds the number required for > creating an query plan after the job starts. > 2. When the crawling performance slows down. For example, if the document > processing rate drops below a specified threshold. > How about adding two parameters to handle the timing of 'ANALYZE' execution > as below? > 1. `org.apache.manifoldcf.db.postgres.analyze..minimumrowcount` > Specify how many records should be accumulated before carrying out an > 'ANALYZE' on the specified table as the first time.defaults to 100. > 2.`org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate` > Specify the number of documents processed in the last minute. If the actual > processing rate falls below this, the 'ANALYZE' will be carrying out. > defaults to 1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1746) Adding execution conditions of PostgreSQL's ANALYZE command to avoid crawling become extremely slow.
Mingchun Zhao created CONNECTORS-1746: - Summary: Adding execution conditions of PostgreSQL's ANALYZE command to avoid crawling become extremely slow. Key: CONNECTORS-1746 URL: https://issues.apache.org/jira/browse/CONNECTORS-1746 Project: ManifoldCF Issue Type: Improvement Components: Web connector Environment: I am using ManifoldCF 2.24 with PostgreSQL 12.14 as the database. Reporter: Mingchun Zhao Sometimes, the crawling does not process any documents for a while and there is nothing logged about long-running queries. The performance can be restored by firing the 'ANALYZE' command manually. It seems that a bad query plan caused this performance problem. Therefore, in addition to the current configuration parameter org.apache.manifoldcf.db.postgres.analyze. , it is considered necessary to execute the 'ANALYZE' even in the following situations. 1. When the number of records in the table exceeds the number required for creating an query plan after the job starts. 2. When the crawling performance slows down. For example, if the document processing rate drops below a specified threshold. How about adding two parameters to handle the timing of 'ANALYZE' execution as below? 1. `org.apache.manifoldcf.db.postgres.analyze..minimumrowcount` Specify how many records should be accumulated before carrying out an 'ANALYZE' on the specified table as the first time.defaults to 100. 2.`org.apache.manifoldcf.db.postgres.analyze..minimumprocessrate` Specify the number of documents processed in the last minute. If the actual processing rate falls below this, the 'ANALYZE' will be carrying out. defaults to 1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1188) Missing Japanese image in end_user_documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14562871#comment-14562871 ] Mingchun Zhao commented on CONNECTORS-1188: --- Committed r1682238(dev_1x). pull up changes r1682232 to the dev_1x branch from trunk. Missing Japanese image in end_user_documentation Key: CONNECTORS-1188 URL: https://issues.apache.org/jira/browse/CONNECTORS-1188 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 1.9, ManifoldCF 2.1 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.10, ManifoldCF 2.2 The image images/ja_JP/ad-configure-cache_ja_JP.PNG is missing. This is preventing us from building release candidates for 1.9 and 2.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1188) Missing Japanese image in end_user_documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14562829#comment-14562829 ] Mingchun Zhao commented on CONNECTORS-1188: --- Committed r1682232(trunk). added an image images/ja_JP/ad-configure-cache_ja_JP.PNG. test: build the project part of the site. $ cd site $ echo $FORREST_HOME /home/mzhao/apache-forrest-0.9 $ echo $JAVA_TOOL_OPTIONS -Dfile.encoding=UTF8 $ forrest site OK. Missing Japanese image in end_user_documentation Key: CONNECTORS-1188 URL: https://issues.apache.org/jira/browse/CONNECTORS-1188 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 1.9, ManifoldCF 2.1 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.10, ManifoldCF 2.2 The image images/ja_JP/ad-configure-cache_ja_JP.PNG is missing. This is preventing us from building release candidates for 1.9 and 2.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14562928#comment-14562928 ] Mingchun Zhao commented on CONNECTORS-853: -- committed r1682252(trunk). patch: end-user-documentation.xml.20150527.patch Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.10, ManifoldCF 2.2 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.20150515.patch, end-user-documentation.xml.20150527.patch, end-user-documentation.xml.ActiveDirectory.patch, end-user-documentation.xml.patch, end-user-documentation.xml.wikirepo.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14562935#comment-14562935 ] Mingchun Zhao commented on CONNECTORS-853: -- committed r1682254(dev_1x). pull up r1682252 to dev_1x from trunk. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.10, ManifoldCF 2.2 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.20150515.patch, end-user-documentation.xml.20150527.patch, end-user-documentation.xml.ActiveDirectory.patch, end-user-documentation.xml.patch, end-user-documentation.xml.wikirepo.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CONNECTORS-1188) Missing Japanese image in end_user_documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao resolved CONNECTORS-1188. --- Resolution: Fixed Missing Japanese image in end_user_documentation Key: CONNECTORS-1188 URL: https://issues.apache.org/jira/browse/CONNECTORS-1188 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 1.9, ManifoldCF 2.1 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.10, ManifoldCF 2.2 The image images/ja_JP/ad-configure-cache_ja_JP.PNG is missing. This is preventing us from building release candidates for 1.9 and 2.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547081#comment-14547081 ] Mingchun Zhao commented on CONNECTORS-853: -- Committed r1679826 into trunk. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.10, ManifoldCF 2.2 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.20150515.patch, end-user-documentation.xml.ActiveDirectory.patch, end-user-documentation.xml.patch, end-user-documentation.xml.wikirepo.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547082#comment-14547082 ] Mingchun Zhao commented on CONNECTORS-853: -- pulls up commit r1679826 to dev_1x branch Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.10, ManifoldCF 2.2 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.20150515.patch, end-user-documentation.xml.ActiveDirectory.patch, end-user-documentation.xml.patch, end-user-documentation.xml.wikirepo.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1188) Missing Japanese image in end_user_documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497920#comment-14497920 ] Mingchun Zhao commented on CONNECTORS-1188: --- Karl, sorry, I noticed this just now. I'll deal with this by the next release. Missing Japanese image in end_user_documentation Key: CONNECTORS-1188 URL: https://issues.apache.org/jira/browse/CONNECTORS-1188 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 1.9, ManifoldCF 2.1 Reporter: Karl Wright Assignee: Mingchun Zhao Priority: Blocker Fix For: ManifoldCF 1.9, ManifoldCF 2.1 The image images/ja_JP/ad-configure-cache_ja_JP.PNG is missing. This is preventing us from building release candidates for 1.9 and 2.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14379780#comment-14379780 ] Mingchun Zhao commented on CONNECTORS-853: -- r1669100(trunk) Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.ActiveDirectory.patch, end-user-documentation.xml.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14379781#comment-14379781 ] Mingchun Zhao commented on CONNECTORS-853: -- r1669101(dev_1x) Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.ActiveDirectory.patch, end-user-documentation.xml.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14379779#comment-14379779 ] Mingchun Zhao commented on CONNECTORS-853: -- Koizumi, thanks! Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.ActiveDirectory.patch, end-user-documentation.xml.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14332067#comment-14332067 ] Mingchun Zhao commented on CONNECTORS-853: -- r1661455(dev_1x) Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326753#comment-14326753 ] Mingchun Zhao commented on CONNECTORS-853: -- Koizumi, thanks! got it. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.patch, end-user-documentation.xml_IBM_FIlenet_P8.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CONNECTORS-1164) Two view buttons in Japanese List of Authority Groups page
[ https://issues.apache.org/jira/browse/CONNECTORS-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao resolved CONNECTORS-1164. --- Resolution: Fixed Two view buttons in Japanese List of Authority Groups page Key: CONNECTORS-1164 URL: https://issues.apache.org/jira/browse/CONNECTORS-1164 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 2.0.1 Reporter: KOIZUMI Satoru Assignee: Mingchun Zhao Priority: Minor Attachments: common_ja_JP.properties.patch There are two view(表示) button in List of Authority Groups(権限グループ一覧) page of Japanese version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14311290#comment-14311290 ] Mingchun Zhao commented on CONNECTORS-853: -- Committed r1658155 into trunk. Regular Expression User Mapping Connection section(document and screenshots) Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304600#comment-14304600 ] Mingchun Zhao commented on CONNECTORS-853: -- Koizumi, thanks! got it. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml, end-user-documentation.xml.patch Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CONNECTORS-1152) Update Japanese document of Technical Resources
[ https://issues.apache.org/jira/browse/CONNECTORS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao reassigned CONNECTORS-1152: - Assignee: Mingchun Zhao Update Japanese document of Technical Resources - Key: CONNECTORS-1152 URL: https://issues.apache.org/jira/browse/CONNECTORS-1152 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 2.0 Reporter: KOIZUMI Satoru Assignee: Mingchun Zhao Priority: Minor Attachments: technical-resources.xml.patch Japanese Technical Resources(開発者リソース) needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295078#comment-14295078 ] Mingchun Zhao commented on CONNECTORS-853: -- 'ant doc' test passed. Committed r1655264. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1152) Update Japanese document of Technical Resources
[ https://issues.apache.org/jira/browse/CONNECTORS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295049#comment-14295049 ] Mingchun Zhao commented on CONNECTORS-1152: --- Committed r1655261 to trunk. Update Japanese document of Technical Resources - Key: CONNECTORS-1152 URL: https://issues.apache.org/jira/browse/CONNECTORS-1152 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 2.0 Reporter: KOIZUMI Satoru Assignee: Mingchun Zhao Priority: Minor Attachments: technical-resources.xml.patch Japanese Technical Resources(開発者リソース) needs to be updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296119#comment-14296119 ] Mingchun Zhao commented on CONNECTORS-853: -- Karl, thanks! Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-853: - Attachment: CONNECTORS-853.patch patch based on changes from Koizumi. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: CONNECTORS-853.patch, end-user-documentation.xml Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-697) Need japanese translations for GoogleDrive connector
[ https://issues.apache.org/jira/browse/CONNECTORS-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14286692#comment-14286692 ] Mingchun Zhao commented on CONNECTORS-697: -- For management, It would be better to create issues for documentations according to its own type, e.g. - end user manual - menu(or button) for connector xxx - menu(or button) for job and so on. Need japanese translations for GoogleDrive connector Key: CONNECTORS-697 URL: https://issues.apache.org/jira/browse/CONNECTORS-697 Project: ManifoldCF Issue Type: Bug Components: GoogleDrive connector Affects Versions: ManifoldCF 1.3 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Need japanese translations for GoogleDrive connector. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-697) Need japanese translations for GoogleDrive connector
[ https://issues.apache.org/jira/browse/CONNECTORS-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14286722#comment-14286722 ] Mingchun Zhao commented on CONNECTORS-697: -- Karl, thanks. got it. Need japanese translations for GoogleDrive connector Key: CONNECTORS-697 URL: https://issues.apache.org/jira/browse/CONNECTORS-697 Project: ManifoldCF Issue Type: Bug Components: GoogleDrive connector Affects Versions: ManifoldCF 1.3 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Need japanese translations for GoogleDrive connector. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1140) improve Japanese End User Manual
[ https://issues.apache.org/jira/browse/CONNECTORS-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14278309#comment-14278309 ] Mingchun Zhao commented on CONNECTORS-1140: --- Koizumi, thank you for your nice patch. Karl, thank you putting this into trunk,dev_1x(I noticed this just now). improve Japanese End User Manual Key: CONNECTORS-1140 URL: https://issues.apache.org/jira/browse/CONNECTORS-1140 Project: ManifoldCF Issue Type: Improvement Components: Documentation Reporter: KOIZUMI Satoru Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Attachments: end-user-documentation.xml.patch Thank you for your Japanese translation. I have made a patch to make it more fluent. I will explain each change if you need. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14272502#comment-14272502 ] Mingchun Zhao commented on CONNECTORS-853: -- Committed r1650742. added the authority groups feature into Japanese end-user-documentation with related screen shots. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF next Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14272516#comment-14272516 ] Mingchun Zhao commented on CONNECTORS-853: -- Committed r1650747. added the Amazon Cloud Search output connector feature into Japanese end-user-documentation with related screen shots. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14272499#comment-14272499 ] Mingchun Zhao commented on CONNECTORS-853: -- Committed r1650741. added the transformation connection feature into Japanese end-user-documentation including related screen shots, and updated corresponding menus in Japanese Framework UI. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF next Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14272524#comment-14272524 ] Mingchun Zhao commented on CONNECTORS-853: -- TODO: #Transformation Connection Types: allowed documents metadata adjuster null transformer tika extractor #User Mapping Connection types regexp mapper Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF 1.9, ManifoldCF 2.1 Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-853) Japanese end-user-documentation needs to be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14230771#comment-14230771 ] Mingchun Zhao commented on CONNECTORS-853: -- Hi Karl, Got it, Let me look into this. Japanese end-user-documentation needs to be updated --- Key: CONNECTORS-853 URL: https://issues.apache.org/jira/browse/CONNECTORS-853 Project: ManifoldCF Issue Type: Task Components: Documentation Affects Versions: ManifoldCF 1.5 Reporter: Karl Wright Assignee: Mingchun Zhao Fix For: ManifoldCF next Japanese end-user-documentation needs to be updated to cover the new features of 1.5. Some new screen shots are needed too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1079) the parsing in TikaExtractor always return empty result
[ https://issues.apache.org/jira/browse/CONNECTORS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184445#comment-14184445 ] Mingchun Zhao commented on CONNECTORS-1079: --- Karl, thanks! It does work pretty well. the parsing in TikaExtractor always return empty result --- Key: CONNECTORS-1079 URL: https://issues.apache.org/jira/browse/CONNECTORS-1079 Project: ManifoldCF Issue Type: Bug Components: Tika extractor Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Karl Wright Fix For: ManifoldCF 1.8, ManifoldCF 2.0 When I use latest trunk source(2.0) to try the Tika content extractor,It did not return any expected results. I looked at it using debugging tools, found that the parser of Tika content extractor does not return any data. I've tried to move lib/tika-core-1.6.jar into connector-lib/, Then, the Tika content extractor returned data as expected. My configurations are as below: == Transformation: Type: Tika content extractor Output: Type:Solr(Use extract update handler=false) Repository: type: Web Job: 1.type: repository 2.type: transformation 3.type: output == Maybe, it is related to CONNECTORS-1074(?), It looks like that the place of tika-core-1.6.jar affects the result of TikaExtractor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CONNECTORS-1084) Missing resource 'WebcrawlerConnector.MatchMustHaveARegexpValue' in bundle 'org.apache.manifoldcf.crawler.connectors.webcrawler.common'
Mingchun Zhao created CONNECTORS-1084: - Summary: Missing resource 'WebcrawlerConnector.MatchMustHaveARegexpValue' in bundle 'org.apache.manifoldcf.crawler.connectors.webcrawler.common' Key: CONNECTORS-1084 URL: https://issues.apache.org/jira/browse/CONNECTORS-1084 Project: ManifoldCF Issue Type: Bug Components: Web connector Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor An error occurred in web connector as below: ERROR 2014-10-24 09:30:19,537 (qtp876209191-368) - Missing resource 'WebcrawlerConnector.MatchMustHaveARegexpValue' in bundle 'org.apache.manifoldcf.crawler.connectors.webcrawler.common' for locale 'ja' java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key WebcrawlerConnector.MatchMustHaveARegexpValue at java.util.ResourceBundle.getObject(ResourceBundle.java:395) at java.util.ResourceBundle.getString(ResourceBundle.java:355) ... ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CONNECTORS-1084) Missing resource 'WebcrawlerConnector.MatchMustHaveARegexpValue' in bundle 'org.apache.manifoldcf.crawler.connectors.webcrawler.common'
[ https://issues.apache.org/jira/browse/CONNECTORS-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao resolved CONNECTORS-1084. --- Resolution: Fixed Fix Version/s: ManifoldCF 2.0 Committed r1634202(trunk). Missing resource 'WebcrawlerConnector.MatchMustHaveARegexpValue' in bundle 'org.apache.manifoldcf.crawler.connectors.webcrawler.common' --- Key: CONNECTORS-1084 URL: https://issues.apache.org/jira/browse/CONNECTORS-1084 Project: ManifoldCF Issue Type: Bug Components: Web connector Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor Fix For: ManifoldCF 2.0 An error occurred in web connector as below: ERROR 2014-10-24 09:30:19,537 (qtp876209191-368) - Missing resource 'WebcrawlerConnector.MatchMustHaveARegexpValue' in bundle 'org.apache.manifoldcf.crawler.connectors.webcrawler.common' for locale 'ja' java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key WebcrawlerConnector.MatchMustHaveARegexpValue at java.util.ResourceBundle.getObject(ResourceBundle.java:395) at java.util.ResourceBundle.getString(ResourceBundle.java:355) ... ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CONNECTORS-1079) the parsing in TikaExtractor always return empty result
[ https://issues.apache.org/jira/browse/CONNECTORS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao reopened CONNECTORS-1079: --- Hi Karl, Thank you for your help, I've tried your fix. Unfortunately, this symptom still occurs even we have two ika-core.jar in both of lib and connector-lib directory. It looks like that the two same jars cause jar conflict. I tried to use ClassLoader to fix it, but gave up eventually. because that makes things more confusing. Could you please confirm my suggestion as below: 1. Get rid of the tika-core.jar from lib directory(need to modify build.xml?) 2. Directly call Tika().detect to get MimeType instead of calling ExtensionMimeMap.mapToMimeType. The related connectors as below(4 files): connectors/filesystem/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/filesystem/FileConnector.java connectors/hdfs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/hdfs/HDFSRepositoryConnector.java connectors/jcifs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharedrive/SharedDriveConnector.java connectors/sharepoint/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharepoint/SharePointRepository.java 3.Delete unused ExtensionMimeMap class which just contains one method to call Tika().detect to get MimeType. framework/core/src/main/java/org/apache/manifoldcf/core/extmimemap/ExtensionMimeMap.java Thanks. the parsing in TikaExtractor always return empty result --- Key: CONNECTORS-1079 URL: https://issues.apache.org/jira/browse/CONNECTORS-1079 Project: ManifoldCF Issue Type: Bug Components: Tika extractor Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Karl Wright Fix For: ManifoldCF 1.8, ManifoldCF 2.0 When I use latest trunk source(2.0) to try the Tika content extractor,It did not return any expected results. I looked at it using debugging tools, found that the parser of Tika content extractor does not return any data. I've tried to move lib/tika-core-1.6.jar into connector-lib/, Then, the Tika content extractor returned data as expected. My configurations are as below: == Transformation: Type: Tika content extractor Output: Type:Solr(Use extract update handler=false) Repository: type: Web Job: 1.type: repository 2.type: transformation 3.type: output == Maybe, it is related to CONNECTORS-1074(?), It looks like that the place of tika-core-1.6.jar affects the result of TikaExtractor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1079) the parsing in TikaExtractor always return empty result
[ https://issues.apache.org/jira/browse/CONNECTORS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184165#comment-14184165 ] Mingchun Zhao edited comment on CONNECTORS-1079 at 10/25/14 5:10 PM: - Hi Karl, Thank you for your help, I've tried your fix. Unfortunately, this symptom still occurs even we have two tika-core.jar in both of lib and connector-lib directory. It looks like that the two same jars cause jar conflict. I tried to use ClassLoader to fix it, but gave up eventually. because that makes things more confusing. Could you please confirm my suggestion as below: 1. Get rid of the tika-core.jar from lib directory(need to modify build.xml?) 2. Directly call Tika().detect to get MimeType instead of calling ExtensionMimeMap.mapToMimeType. The related connectors as below(4 files): connectors/filesystem/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/filesystem/FileConnector.java connectors/hdfs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/hdfs/HDFSRepositoryConnector.java connectors/jcifs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharedrive/SharedDriveConnector.java connectors/sharepoint/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharepoint/SharePointRepository.java 3.Delete unused ExtensionMimeMap class which just contains one method to call Tika().detect to get MimeType. framework/core/src/main/java/org/apache/manifoldcf/core/extmimemap/ExtensionMimeMap.java Thanks. was (Author: mingchun.zhao): Hi Karl, Thank you for your help, I've tried your fix. Unfortunately, this symptom still occurs even we have two ika-core.jar in both of lib and connector-lib directory. It looks like that the two same jars cause jar conflict. I tried to use ClassLoader to fix it, but gave up eventually. because that makes things more confusing. Could you please confirm my suggestion as below: 1. Get rid of the tika-core.jar from lib directory(need to modify build.xml?) 2. Directly call Tika().detect to get MimeType instead of calling ExtensionMimeMap.mapToMimeType. The related connectors as below(4 files): connectors/filesystem/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/filesystem/FileConnector.java connectors/hdfs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/hdfs/HDFSRepositoryConnector.java connectors/jcifs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharedrive/SharedDriveConnector.java connectors/sharepoint/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharepoint/SharePointRepository.java 3.Delete unused ExtensionMimeMap class which just contains one method to call Tika().detect to get MimeType. framework/core/src/main/java/org/apache/manifoldcf/core/extmimemap/ExtensionMimeMap.java Thanks. the parsing in TikaExtractor always return empty result --- Key: CONNECTORS-1079 URL: https://issues.apache.org/jira/browse/CONNECTORS-1079 Project: ManifoldCF Issue Type: Bug Components: Tika extractor Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Karl Wright Fix For: ManifoldCF 1.8, ManifoldCF 2.0 When I use latest trunk source(2.0) to try the Tika content extractor,It did not return any expected results. I looked at it using debugging tools, found that the parser of Tika content extractor does not return any data. I've tried to move lib/tika-core-1.6.jar into connector-lib/, Then, the Tika content extractor returned data as expected. My configurations are as below: == Transformation: Type: Tika content extractor Output: Type:Solr(Use extract update handler=false) Repository: type: Web Job: 1.type: repository 2.type: transformation 3.type: output == Maybe, it is related to CONNECTORS-1074(?), It looks like that the place of tika-core-1.6.jar affects the result of TikaExtractor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1079) the parsing in TikaExtractor always return empty result
[ https://issues.apache.org/jira/browse/CONNECTORS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184165#comment-14184165 ] Mingchun Zhao edited comment on CONNECTORS-1079 at 10/25/14 5:11 PM: - Hi Karl, Thank you for your help, I've tried your fix. Unfortunately, this symptom still occurs even though we have two tika-core.jar in both of lib and connector-lib directory. It looks like that the two same jars cause jar conflict. I tried to use ClassLoader to fix it, but gave up eventually. because that makes things more confusing. Could you please confirm my suggestion as below: 1. Get rid of the tika-core.jar from lib directory(need to modify build.xml?) 2. Directly call Tika().detect to get MimeType instead of calling ExtensionMimeMap.mapToMimeType. The related connectors as below(4 files): connectors/filesystem/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/filesystem/FileConnector.java connectors/hdfs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/hdfs/HDFSRepositoryConnector.java connectors/jcifs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharedrive/SharedDriveConnector.java connectors/sharepoint/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharepoint/SharePointRepository.java 3.Delete unused ExtensionMimeMap class which just contains one method to call Tika().detect to get MimeType. framework/core/src/main/java/org/apache/manifoldcf/core/extmimemap/ExtensionMimeMap.java Thanks. was (Author: mingchun.zhao): Hi Karl, Thank you for your help, I've tried your fix. Unfortunately, this symptom still occurs even we have two tika-core.jar in both of lib and connector-lib directory. It looks like that the two same jars cause jar conflict. I tried to use ClassLoader to fix it, but gave up eventually. because that makes things more confusing. Could you please confirm my suggestion as below: 1. Get rid of the tika-core.jar from lib directory(need to modify build.xml?) 2. Directly call Tika().detect to get MimeType instead of calling ExtensionMimeMap.mapToMimeType. The related connectors as below(4 files): connectors/filesystem/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/filesystem/FileConnector.java connectors/hdfs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/hdfs/HDFSRepositoryConnector.java connectors/jcifs/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharedrive/SharedDriveConnector.java connectors/sharepoint/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/sharepoint/SharePointRepository.java 3.Delete unused ExtensionMimeMap class which just contains one method to call Tika().detect to get MimeType. framework/core/src/main/java/org/apache/manifoldcf/core/extmimemap/ExtensionMimeMap.java Thanks. the parsing in TikaExtractor always return empty result --- Key: CONNECTORS-1079 URL: https://issues.apache.org/jira/browse/CONNECTORS-1079 Project: ManifoldCF Issue Type: Bug Components: Tika extractor Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Karl Wright Fix For: ManifoldCF 1.8, ManifoldCF 2.0 When I use latest trunk source(2.0) to try the Tika content extractor,It did not return any expected results. I looked at it using debugging tools, found that the parser of Tika content extractor does not return any data. I've tried to move lib/tika-core-1.6.jar into connector-lib/, Then, the Tika content extractor returned data as expected. My configurations are as below: == Transformation: Type: Tika content extractor Output: Type:Solr(Use extract update handler=false) Repository: type: Web Job: 1.type: repository 2.type: transformation 3.type: output == Maybe, it is related to CONNECTORS-1074(?), It looks like that the place of tika-core-1.6.jar affects the result of TikaExtractor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1079) the parsing in TikaExtractor always return empty result
[ https://issues.apache.org/jira/browse/CONNECTORS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184307#comment-14184307 ] Mingchun Zhao commented on CONNECTORS-1079: --- The first thing to check is how big the build binary will be if every tika jar is at the root level. Thanks, I'll confirm this. the parsing in TikaExtractor always return empty result --- Key: CONNECTORS-1079 URL: https://issues.apache.org/jira/browse/CONNECTORS-1079 Project: ManifoldCF Issue Type: Bug Components: Tika extractor Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Karl Wright Fix For: ManifoldCF 1.8, ManifoldCF 2.0 When I use latest trunk source(2.0) to try the Tika content extractor,It did not return any expected results. I looked at it using debugging tools, found that the parser of Tika content extractor does not return any data. I've tried to move lib/tika-core-1.6.jar into connector-lib/, Then, the Tika content extractor returned data as expected. My configurations are as below: == Transformation: Type: Tika content extractor Output: Type:Solr(Use extract update handler=false) Repository: type: Web Job: 1.type: repository 2.type: transformation 3.type: output == Maybe, it is related to CONNECTORS-1074(?), It looks like that the place of tika-core-1.6.jar affects the result of TikaExtractor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1005) Chinese Localization(Documentation, Screen shots)
[ https://issues.apache.org/jira/browse/CONNECTORS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151001#comment-14151001 ] Mingchun Zhao commented on CONNECTORS-1005: --- Committed r1628046. part of Localization in Chinese(Simplified) and Japanese. Chinese Localization(Documentation, Screen shots) - Key: CONNECTORS-1005 URL: https://issues.apache.org/jira/browse/CONNECTORS-1005 Project: ManifoldCF Issue Type: Task Components: Documentation Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor Fix For: ManifoldCF 2.0 Derived from (CONNECTORS-987) Chinese Localization(Documentation, Help screens) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CONNECTORS-1005) Chinese Localization(Documentation, Screen shots)
[ https://issues.apache.org/jira/browse/CONNECTORS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao resolved CONNECTORS-1005. --- Resolution: Fixed Chinese Localization(Documentation, Screen shots) - Key: CONNECTORS-1005 URL: https://issues.apache.org/jira/browse/CONNECTORS-1005 Project: ManifoldCF Issue Type: Task Components: Documentation Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor Fix For: ManifoldCF 2.0 Derived from (CONNECTORS-987) Chinese Localization(Documentation, Help screens) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1005) Chinese Localization(Documentation, Screen shots)
[ https://issues.apache.org/jira/browse/CONNECTORS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146081#comment-14146081 ] Mingchun Zhao commented on CONNECTORS-1005: --- Hi Karl, I still have something to do in this ticket, so I'd like to keep it open for now. Thanks! Chinese Localization(Documentation, Screen shots) - Key: CONNECTORS-1005 URL: https://issues.apache.org/jira/browse/CONNECTORS-1005 Project: ManifoldCF Issue Type: Task Components: Documentation Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor Fix For: ManifoldCF 2.0 Derived from (CONNECTORS-987) Chinese Localization(Documentation, Help screens) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CONNECTORS-1005) Chinese Localization(Documentation, Screen shots)
[ https://issues.apache.org/jira/browse/CONNECTORS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14133747#comment-14133747 ] Mingchun Zhao edited comment on CONNECTORS-1005 at 9/15/14 12:17 PM: - Committed r1624982. fixed the following issue: Some buttons on page of OutputConnection are displayed in English even in either Chinese locale or Japanese locale. was (Author: mingchun.zhao): fixed the following issue: Some buttons on page of OutputConnection are displayed in English even in either Chinese locale or Japanese locale. Chinese Localization(Documentation, Screen shots) - Key: CONNECTORS-1005 URL: https://issues.apache.org/jira/browse/CONNECTORS-1005 Project: ManifoldCF Issue Type: Task Components: Documentation Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor Fix For: ManifoldCF 2.0 Derived from (CONNECTORS-987) Chinese Localization(Documentation, Help screens) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1005) Chinese Localization(Documentation, Screen shots)
[ https://issues.apache.org/jira/browse/CONNECTORS-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14133825#comment-14133825 ] Mingchun Zhao commented on CONNECTORS-1005: --- Committed r1624985. deal with chinese localization to amazoncloudsearch Chinese Localization(Documentation, Screen shots) - Key: CONNECTORS-1005 URL: https://issues.apache.org/jira/browse/CONNECTORS-1005 Project: ManifoldCF Issue Type: Task Components: Documentation Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor Fix For: ManifoldCF 2.0 Derived from (CONNECTORS-987) Chinese Localization(Documentation, Help screens) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CONNECTORS-1005) Chinese Localization(Documentation, Screen shots)
Mingchun Zhao created CONNECTORS-1005: - Summary: Chinese Localization(Documentation, Screen shots) Key: CONNECTORS-1005 URL: https://issues.apache.org/jira/browse/CONNECTORS-1005 Project: ManifoldCF Issue Type: Task Components: Documentation Reporter: Mingchun Zhao Assignee: Mingchun Zhao Priority: Minor Fix For: ManifoldCF 2.0 Derived from (CONNECTORS-987) Chinese Localization(Documentation, Help screens) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092554#comment-14092554 ] Mingchun Zhao commented on CONNECTORS-987: -- Hi Karl, I've opened a new ticket for the uncompleted work. https://issues.apache.org/jira/browse/CONNECTORS-1005 Thanks, Mingchun Zhao Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao resolved CONNECTORS-987. -- Resolution: Fixed Opened a new ticket for the uncompleted task. https://issues.apache.org/jira/browse/CONNECTORS-1005 Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092052#comment-14092052 ] Mingchun Zhao commented on CONNECTORS-987: -- Hi Karl, I've just committed this issue. There are two things I want to ask you. 1. How should I deal with the BOM in UTF-8 for ManifoldCF. BTW, I wrote files in UTF-8 without appending BOM in this issue. 2.There still are some screenshots unfinished. Would I have it done in the next version(2.0)? BEST, Mingchun Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092080#comment-14092080 ] Mingchun Zhao commented on CONNECTORS-987: -- Hi Karl, Thanks for your reply and advice. Utf-8 is much more convenient unless you have extended characters, and then I would not be sure Forrest would work with them properly either. Actually, when I put my changes into svn, there were already some UTF-8 files(including Japanese in it). And I noticed that, some of them included BOM, when the others didn't. This is why I asked you for it. As for uncompleted pages, please just leave those in English, and we will work on them later Got it. Thanks. Regards, Mingchun Zhao Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092291#comment-14092291 ] Mingchun Zhao commented on CONNECTORS-987: -- Hi Karl, I've already fixed that in my last commit yesterday. The following files had the BOM in them. site/src/documentation/content/xdocs/site.xml site/src/documentation/content/xdocs/tabs.xml Here is the difference between The old and new one, The 3bytes EF BB BF at the beginning of site.xml-old is showing the BOM. pre $ od -cX ./site/src/documentation/content/xdocs/site.xml-old | head 000 357 273 277 ? x m l v e r s i o n 3cbfbbef6c6d783f726576206e6f6973 020= 1 . 0 e n c o d i n g = 2e31223d65202230646f636e3d676e69 040 u t f - 8 ? \n ! - - \n 667475223f22382d213c0a3e200a2d2d 060C o p y r i g h t 2 0 0 2 - 706f432067697279322074682d323030 1002 0 0 4 T h e A p a c h e 34303032656854206170412020656863 $ od -cX ./site/src/documentation/content/xdocs/site.xml-new | head 000 ? x m l v e r s i o n = 1 6d783f3c6576206c6f69737231223d6e 020. 0 e n c o d i n g = u t 2022302e6f636e65676e69647475223d 040f - 8 ? \n ! - - \n C o 22382d663c0a3e3f0a2d2d216f432020 060p y r i g h t 2 0 0 2 - 2 0 0 6972797020746867323030323030322d 1004 T h e A p a c h e S o f 685420347041206565686361666f5320 /pre BEST, Mingchun Zhao Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092319#comment-14092319 ] Mingchun Zhao commented on CONNECTORS-987: -- Hi Karl, It looks like it will be a big task to make Chinese screen shots, So, could I just leave those screen shots in English for the time being? Regards, Mingchun Zhao Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084455#comment-14084455 ] Mingchun Zhao commented on CONNECTORS-987: -- Hi Karl, Would you kindly confirm this issue? I'm trying to make the end-user-documentation.pdf for the Chinese language. The thing is I could not find a suitable Chinese font to make a PDF file. Of course, we will be able to make the end-user-documentation.html for Chinese. Regards, Mingchun Zhao Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071283#comment-14071283 ] Mingchun Zhao commented on CONNECTORS-987: -- Hi Karl, Got it. I plan to finish up this issue by August 15. BEST Mingchun Zhao Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 1.7 Reporter: Mingchun Zhao Assignee: Mingchun Zhao Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
Mingchun Zhao created CONNECTORS-987: Summary: Chinese Localization(Documentation, Help screens) Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Reporter: Mingchun Zhao -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-987: - Description: In this issue, I will deal with documentation,help screens for Chinese Localization. Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Reporter: Mingchun Zhao In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CONNECTORS-987) Chinese Localization(Documentation, Help screens)
[ https://issues.apache.org/jira/browse/CONNECTORS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-987: - Attachment: CONNECTORS-987.patch A patch for the first time(5 files added). Chinese Localization(Documentation, Help screens) - Key: CONNECTORS-987 URL: https://issues.apache.org/jira/browse/CONNECTORS-987 Project: ManifoldCF Issue Type: Improvement Components: Documentation Reporter: Mingchun Zhao Attachments: CONNECTORS-987.patch In this issue, I will deal with documentation,help screens for Chinese Localization. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CONNECTORS-933) Chinese Localization
[ https://issues.apache.org/jira/browse/CONNECTORS-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-933: - Attachment: CONNECTORS-933.patch Hi Karl, Could you please confirm my new patch? Thank you so much. #added 5 files connectors/documentum/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/authorities/DCTM/common_zh_CN.properties connectors/sharepoint/connector/src/main/native2ascii/org/apache/manifoldcf/authorities/authorities/sharepoint/common_zh_CN.properties connectors/filenet/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/filenet/common_zh_CN.properties connectors/solr/connector/src/main/native2ascii/org/apache/manifoldcf/agents/output/solr/common_zh_CN.properties connectors/jcifs/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/sharedrive/common_zh_CN.properties Best regards, Mingchun Zhao Chinese Localization Key: CONNECTORS-933 URL: https://issues.apache.org/jira/browse/CONNECTORS-933 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 1.5.1 Reporter: Mingchun Zhao Assignee: Karl Wright Labels: chinese, localization Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-933.patch, CONNECTORS-933.patch, CONNECTORS-933.patch Original Estimate: 1,344h Remaining Estimate: 1,344h I looked at ManifoldCF and it looks like Chinese is not supported. So, I'd like to contribute a Chinese Localization(Simplified Chinese(zh_CN) for now). As the first step to the goal, I've tried to deal with main screens of the ManifoldCF. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CONNECTORS-933) Chinese Localization
[ https://issues.apache.org/jira/browse/CONNECTORS-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingchun Zhao updated CONNECTORS-933: - Attachment: CONNECTORS-933.patch In this patch, I've dealt with 5 files as below: #modified(1 file) framework/ui-core/src/main/native2ascii/org/apache/manifoldcf/ui/i18n/common_zh_CN.properties #added(4 files) connectors/livelink/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/livelink/common_zh_CN.properties connectors/meridio/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/meridio/common_zh_CN.properties connectors/sharepoint/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/sharepoint/common_zh_CN.properties connectors/webcrawler/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/webcrawler/common_zh_CN.properties Chinese Localization Key: CONNECTORS-933 URL: https://issues.apache.org/jira/browse/CONNECTORS-933 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 1.5.1 Reporter: Mingchun Zhao Assignee: Karl Wright Labels: chinese, localization Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-933.patch, CONNECTORS-933.patch Original Estimate: 1,344h Remaining Estimate: 1,344h I looked at ManifoldCF and it looks like Chinese is not supported. So, I'd like to contribute a Chinese Localization(Simplified Chinese(zh_CN) for now). As the first step to the goal, I've tried to deal with main screens of the ManifoldCF. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CONNECTORS-933) Chinese Localization
[ https://issues.apache.org/jira/browse/CONNECTORS-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988978#comment-13988978 ] Mingchun Zhao edited comment on CONNECTORS-933 at 5/4/14 12:48 PM: --- In today's patch, I've dealt with 5 files as below: #modified(1 file) framework/ui-core/src/main/native2ascii/org/apache/manifoldcf/ui/i18n/common_zh_CN.properties #added(4 files) connectors/livelink/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/livelink/common_zh_CN.properties connectors/meridio/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/meridio/common_zh_CN.properties connectors/sharepoint/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/sharepoint/common_zh_CN.properties connectors/webcrawler/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/webcrawler/common_zh_CN.properties was (Author: mingchun.zhao): In this patch, I've dealt with 5 files as below: #modified(1 file) framework/ui-core/src/main/native2ascii/org/apache/manifoldcf/ui/i18n/common_zh_CN.properties #added(4 files) connectors/livelink/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/livelink/common_zh_CN.properties connectors/meridio/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/meridio/common_zh_CN.properties connectors/sharepoint/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/sharepoint/common_zh_CN.properties connectors/webcrawler/connector/src/main/native2ascii/org/apache/manifoldcf/crawler/connectors/webcrawler/common_zh_CN.properties Chinese Localization Key: CONNECTORS-933 URL: https://issues.apache.org/jira/browse/CONNECTORS-933 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 1.5.1 Reporter: Mingchun Zhao Assignee: Karl Wright Labels: chinese, localization Fix For: ManifoldCF 1.7 Attachments: CONNECTORS-933.patch, CONNECTORS-933.patch Original Estimate: 1,344h Remaining Estimate: 1,344h I looked at ManifoldCF and it looks like Chinese is not supported. So, I'd like to contribute a Chinese Localization(Simplified Chinese(zh_CN) for now). As the first step to the goal, I've tried to deal with main screens of the ManifoldCF. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CONNECTORS-933) Chinese Localization
Mingchun Zhao created CONNECTORS-933: Summary: Chinese Localization Key: CONNECTORS-933 URL: https://issues.apache.org/jira/browse/CONNECTORS-933 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 1.5.1 Reporter: Mingchun Zhao Fix For: ManifoldCF next I looked at ManifoldCF and it looks like Chinese is not supported. So, I'd like to contribute a Chinese Localization(Simplified Chinese(zh_CN) for now). As the first step to the goal, I've tried to deal with main screens of the ManifoldCF. -- This message was sent by Atlassian JIRA (v6.2#6252)
