[jira] [Commented] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446872#comment-16446872 ] Karl Wright commented on CONNECTORS-1495: - It sounds like you're missing a doxia plugin for Chinese. But I can't find this error message in any online document. > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONNECTORS-1495) Brand new website
[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446856#comment-16446856
]
Piergiorgio Lucidi commented on CONNECTORS-1495:
I have added a first version of the website with also the chinese and japanese
contents generated using the Forrest2md plugin. I attached a screenshot:
!ManifoldCF-FluidoSkin.png|width=641,height=350!
For seeing the new website you only need to run:
{{mvn clean site:run}}
I actually have an issue when trying to render the chinese website using the
zh_CN locale with the following exception returned, any ideas?
{{HTTP ERROR 500}}
{{Problem accessing /zh/index.html. Reason:}}{{ No doxia bean found for the
locale zh_CN}}{{ }}
{{Caused by:}}{{javax.servlet.ServletException: No doxia bean found for the
locale zh_CN at
org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129) at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440) at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at
org.mortbay.jetty.Server.handle(Server.java:326) at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) }}
> Brand new website
> -
>
> Key: CONNECTORS-1495
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
> Project: ManifoldCF
> Issue Type: New Feature
> Components: Site
>Affects Versions: ManifoldCF 2.9.1
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
> Fix For: ManifoldCF next
>
> Attachments: ManifoldCF-FluidoSkin.png
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website
> template to use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/]
> template.
> [~molgun] proposed this approach:
> # Find a modern new static site generator like Jekyll [1]
> # Create a template
> # Start to use it in a specific path like
> [https://manifoldcf.apache.org/*new*]
> # Migrate our Forrest xml's to Markdown (we can automate this somehow)
> # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CONNECTORS-1495) Brand new website
[ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi updated CONNECTORS-1495: --- Attachment: ManifoldCF-FluidoSkin.png > Brand new website > - > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1495 > Project: ManifoldCF > Issue Type: New Feature > Components: Site >Affects Versions: ManifoldCF 2.9.1 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi >Priority: Major > Fix For: ManifoldCF next > > Attachments: ManifoldCF-FluidoSkin.png > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website > template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] > template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like > [https://manifoldcf.apache.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1] [https://jekyllrb.com/docs/home/] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONNECTORS-1503) UpdateProcessor SolrCloud and ManifoldCF
[ https://issues.apache.org/jira/browse/CONNECTORS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446762#comment-16446762 ] Karl Wright commented on CONNECTORS-1503: - Thank you, Abe-san. [~Moltroon], can you once again repeat Abe-san's steps, and see if you see the same results? > UpdateProcessor SolrCloud and ManifoldCF > > > Key: CONNECTORS-1503 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1503 > Project: ManifoldCF > Issue Type: Bug > Components: Solr 6.x component >Affects Versions: ManifoldCF 2.9.1 > Environment: SolrCloud 6.6 > ManifoldCF 2.9.1 >Reporter: Maxence SAUNIER >Assignee: Shinichiro Abe >Priority: Major > Attachments: 20170421-1740.png, jira_update_processor.png > > > Hello, > [Link to Apache mail > archive|http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201804.mbox/%3C079e01d3d7da%24807b8f60%248172ae20%24%40citya.com%3E] > When we used Argument option in ManifoldCF for SolrCloud, ManifoldCF add they > arguments on the POST request and not on the url parameters. So, for add a > (pre)processor or a post-processor with the url, it's not possible. > [SolrConfig > updateRequestProcessorChain|https://lucene.apache.org/solr/guide/6_6/config-api.html#ConfigAPI-Whatabout_updateRequestProcessorChain_] > [call > UpdateRequestProcessors|https://lucene.apache.org/solr/guide/6_6/update-request-processors.html#UpdateRequestProcessors-Processor_Post-ProcessorRequestParameters] > [Conf image|https://image.ibb.co/cZC8bn/jira_update_processor.png] > Solr response: > org.apache.solr.common.SolrException: ERROR: > [doc=file:/srvics01/ways_holding/gestion_ged/gerance/3573/201102081135_ENVOIDEVISPP.doc] > unknown field 'processor' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CONNECTORS-1442) Initial implementation of the Alfresco BFSI Output Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi reassigned CONNECTORS-1442: -- Assignee: Luis Cabaceira (was: Piergiorgio Lucidi) I have assigned this issue directly to [~lcabaceira]. Hope to see this issue completed in the next release :P > Initial implementation of the Alfresco BFSI Output Connector > > > Key: CONNECTORS-1442 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1442 > Project: ManifoldCF > Issue Type: Task > Components: Alfresco BFSI Output Connector >Reporter: Piergiorgio Lucidi >Assignee: Luis Cabaceira >Priority: Major > Fix For: ManifoldCF 2.11 > > Attachments: alfresco-bfsi.zip > > Original Estimate: 504h > Remaining Estimate: 504h > > Luis Cabaceira (Solutions Architect @ Alfresco) contacted me for contributing > in the project with a brand new connector dedicated to massive contents > migration against an Alfresco repository. > Alfresco provides a Bulk File System Import tool that allow to import > contents written in its own format in the file system: > http://docs.alfresco.com/5.2/concepts/Bulk-Import-Tool.html > Basically binaries with also versions and metadata written in the Java > Properties format. > The most important functionality provided by this tool is the in-place > feature. > Using it you can import contents directly inside the content store of > Alfresco in the file system and then import only nodes without the need to > upload/stream binary contents. > This new ManifoldCF connector will convert and write all the crawled contents > in the BFSI format in the remote file system. > In this way the extracted content can be dropped directly in the Alfresco > content store and then running the BFSI tool the repository will import > contents without uploading/streaming any binary. > This is important because the BFSI tool is developed and fully supported by > Alfresco. > If some development will be required for adapting it with ManifoldCF, this > will be done by Luis with also my support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONNECTORS-1503) UpdateProcessor SolrCloud and ManifoldCF
[ https://issues.apache.org/jira/browse/CONNECTORS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446681#comment-16446681 ] Shinichiro Abe commented on CONNECTORS-1503: attached my config, in that case, f1_ss field value is "a", which is unique value through Solr' URP. But when I remove that processor argument, f1_ss field value is ["a", "a"], it has two values. As far as I know, that URP works via HttpPoster. > UpdateProcessor SolrCloud and ManifoldCF > > > Key: CONNECTORS-1503 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1503 > Project: ManifoldCF > Issue Type: Bug > Components: Solr 6.x component >Affects Versions: ManifoldCF 2.9.1 > Environment: SolrCloud 6.6 > ManifoldCF 2.9.1 >Reporter: Maxence SAUNIER >Assignee: Shinichiro Abe >Priority: Major > Attachments: 20170421-1740.png, jira_update_processor.png > > > Hello, > [Link to Apache mail > archive|http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201804.mbox/%3C079e01d3d7da%24807b8f60%248172ae20%24%40citya.com%3E] > When we used Argument option in ManifoldCF for SolrCloud, ManifoldCF add they > arguments on the POST request and not on the url parameters. So, for add a > (pre)processor or a post-processor with the url, it's not possible. > [SolrConfig > updateRequestProcessorChain|https://lucene.apache.org/solr/guide/6_6/config-api.html#ConfigAPI-Whatabout_updateRequestProcessorChain_] > [call > UpdateRequestProcessors|https://lucene.apache.org/solr/guide/6_6/update-request-processors.html#UpdateRequestProcessors-Processor_Post-ProcessorRequestParameters] > [Conf image|https://image.ibb.co/cZC8bn/jira_update_processor.png] > Solr response: > org.apache.solr.common.SolrException: ERROR: > [doc=file:/srvics01/ways_holding/gestion_ged/gerance/3573/201102081135_ENVOIDEVISPP.doc] > unknown field 'processor' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CONNECTORS-1503) UpdateProcessor SolrCloud and ManifoldCF
[ https://issues.apache.org/jira/browse/CONNECTORS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichiro Abe updated CONNECTORS-1503: --- Attachment: 20170421-1740.png > UpdateProcessor SolrCloud and ManifoldCF > > > Key: CONNECTORS-1503 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1503 > Project: ManifoldCF > Issue Type: Bug > Components: Solr 6.x component >Affects Versions: ManifoldCF 2.9.1 > Environment: SolrCloud 6.6 > ManifoldCF 2.9.1 >Reporter: Maxence SAUNIER >Assignee: Shinichiro Abe >Priority: Major > Attachments: 20170421-1740.png, jira_update_processor.png > > > Hello, > [Link to Apache mail > archive|http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201804.mbox/%3C079e01d3d7da%24807b8f60%248172ae20%24%40citya.com%3E] > When we used Argument option in ManifoldCF for SolrCloud, ManifoldCF add they > arguments on the POST request and not on the url parameters. So, for add a > (pre)processor or a post-processor with the url, it's not possible. > [SolrConfig > updateRequestProcessorChain|https://lucene.apache.org/solr/guide/6_6/config-api.html#ConfigAPI-Whatabout_updateRequestProcessorChain_] > [call > UpdateRequestProcessors|https://lucene.apache.org/solr/guide/6_6/update-request-processors.html#UpdateRequestProcessors-Processor_Post-ProcessorRequestParameters] > [Conf image|https://image.ibb.co/cZC8bn/jira_update_processor.png] > Solr response: > org.apache.solr.common.SolrException: ERROR: > [doc=file:/srvics01/ways_holding/gestion_ged/gerance/3573/201102081135_ENVOIDEVISPP.doc] > unknown field 'processor' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CONNECTORS-1503) UpdateProcessor SolrCloud and ManifoldCF
[ https://issues.apache.org/jira/browse/CONNECTORS-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446660#comment-16446660 ] Karl Wright commented on CONNECTORS-1503: - [~shinichiro abe], it seems like not getting an error from Solr is not enough, if it doesn't work either. Are you able to get a "processor" selection via the ManifoldCF Solr Output Connector to work in Solr? > UpdateProcessor SolrCloud and ManifoldCF > > > Key: CONNECTORS-1503 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1503 > Project: ManifoldCF > Issue Type: Bug > Components: Solr 6.x component >Affects Versions: ManifoldCF 2.9.1 > Environment: SolrCloud 6.6 > ManifoldCF 2.9.1 >Reporter: Maxence SAUNIER >Assignee: Shinichiro Abe >Priority: Major > Attachments: jira_update_processor.png > > > Hello, > [Link to Apache mail > archive|http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201804.mbox/%3C079e01d3d7da%24807b8f60%248172ae20%24%40citya.com%3E] > When we used Argument option in ManifoldCF for SolrCloud, ManifoldCF add they > arguments on the POST request and not on the url parameters. So, for add a > (pre)processor or a post-processor with the url, it's not possible. > [SolrConfig > updateRequestProcessorChain|https://lucene.apache.org/solr/guide/6_6/config-api.html#ConfigAPI-Whatabout_updateRequestProcessorChain_] > [call > UpdateRequestProcessors|https://lucene.apache.org/solr/guide/6_6/update-request-processors.html#UpdateRequestProcessors-Processor_Post-ProcessorRequestParameters] > [Conf image|https://image.ibb.co/cZC8bn/jira_update_processor.png] > Solr response: > org.apache.solr.common.SolrException: ERROR: > [doc=file:/srvics01/ways_holding/gestion_ged/gerance/3573/201102081135_ENVOIDEVISPP.doc] > unknown field 'processor' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
