[jira] [Commented] (CONNECTORS-402) Separate the proprietary / non-proprietary deliverables for each connector
[ https://issues.apache.org/jira/browse/CONNECTORS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204496#comment-13204496 ] Karl Wright commented on CONNECTORS-402: I decided to implement the second solution. So now the outstanding issues are down to (2), (3), and (4). Separate the proprietary / non-proprietary deliverables for each connector -- Key: CONNECTORS-402 URL: https://issues.apache.org/jira/browse/CONNECTORS-402 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Piergiorgio Lucidi Assignee: Karl Wright Fix For: ManifoldCF 0.5 Original Estimate: 24h Remaining Estimate: 24h As we have spoken today this ticket is dedicated to try to work on the build process to separate proprietary and non-proprietary libraries in the release package. In this way, for example, we could have a standard way to release a specific library for the connector (mcf-alfresco-connector) without release proprietary libraries and allow users to add proprietary libraries in a specific folder connector-lib-proprietary that could be added to the ManifoldCF classloader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-402) Separate the proprietary / non-proprietary deliverables for each connector
[ https://issues.apache.org/jira/browse/CONNECTORS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13204758#comment-13204758 ] Karl Wright commented on CONNECTORS-402: Fixed the tests, I think. Separate the proprietary / non-proprietary deliverables for each connector -- Key: CONNECTORS-402 URL: https://issues.apache.org/jira/browse/CONNECTORS-402 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Piergiorgio Lucidi Assignee: Karl Wright Fix For: ManifoldCF 0.5 Original Estimate: 24h Remaining Estimate: 24h As we have spoken today this ticket is dedicated to try to work on the build process to separate proprietary and non-proprietary libraries in the release package. In this way, for example, we could have a standard way to release a specific library for the connector (mcf-alfresco-connector) without release proprietary libraries and allow users to add proprietary libraries in a specific folder connector-lib-proprietary that could be added to the ManifoldCF classloader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-403) Sidecar processes require a different MCF_HOME setting than webapps and agents process
Sidecar processes require a different MCF_HOME setting than webapps and agents process -- Key: CONNECTORS-403 URL: https://issues.apache.org/jira/browse/CONNECTORS-403 Project: ManifoldCF Issue Type: Bug Components: Build, Framework crawler agent Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Sidecar processes were moved directly under the dist directory in 0.4-incubating. Unfortunately this means that the sidecar process scripts, which use the environment variable MCF_HOME, require a different MCF_HOME than the main processes and web apps. MCF_HOME is defined by these to be the location of properties.xml. The fix for the ticket is to modify the sidecar process scripts to use the same definition for MCF_HOME. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-403) Sidecar processes require a different MCF_HOME setting than webapps and agents process
[ https://issues.apache.org/jira/browse/CONNECTORS-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-403. Resolution: Fixed r1242561 Sidecar processes require a different MCF_HOME setting than webapps and agents process -- Key: CONNECTORS-403 URL: https://issues.apache.org/jira/browse/CONNECTORS-403 Project: ManifoldCF Issue Type: Bug Components: Build, Framework crawler agent Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Sidecar processes were moved directly under the dist directory in 0.4-incubating. Unfortunately this means that the sidecar process scripts, which use the environment variable MCF_HOME, require a different MCF_HOME than the main processes and web apps. MCF_HOME is defined by these to be the location of properties.xml. The fix for the ticket is to modify the sidecar process scripts to use the same definition for MCF_HOME. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-288) An ElasticSearch connector would be helpful
[
https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Stancapiano updated CONNECTORS-288:
Attachment: manifold-elasticsearch-patch
In this new patch:
1 - I added a new configuration type: indexType. It is mandatory for operations
of update. Here an example of update through http:
curl -XPUT http://localhost:9200/${indexName}/${indexType}/_update -d {}
2 - I parse the output message. Here two examples of output messages in
elasticSearch:
Succesfull:
{ok:true,_index:index,_type:aa,_id:_update,_version:1}
I take the field: ok. If true the operation is succesfull
Error:
{error:ElasticSearchParseException[Failed to derive xcontent from (offset=0,
length=0): []],status:500}
If there is not the ok field, I take the error field and I print the value
as message error
An ElasticSearch connector would be helpful
---
Key: CONNECTORS-288
URL: https://issues.apache.org/jira/browse/CONNECTORS-288
Project: ManifoldCF
Issue Type: New Feature
Affects Versions: ManifoldCF 0.5
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Labels: elasticsearch
Fix For: ManifoldCF next
Attachments: manifold-elasticsearch-patch,
manifold-elasticsearch-patch, manifoldcf-elasticsearch-project-patct
Original Estimate: 120h
Remaining Estimate: 120h
An ElasticSearch connector could be very useful to spread the use of
ManifoldCF
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13205062#comment-13205062 ] Karl Wright commented on CONNECTORS-288: I committed the latest patch. One thing I noticed is that you are not using HTTP connection pooling. In a real system this would lead to problems. I'd suggest you have a look at MultiThreadedHttpConnectionManager; there are examples online that demonstrate reasonable usage. An ElasticSearch connector would be helpful --- Key: CONNECTORS-288 URL: https://issues.apache.org/jira/browse/CONNECTORS-288 Project: ManifoldCF Issue Type: New Feature Affects Versions: ManifoldCF 0.5 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Labels: elasticsearch Fix For: ManifoldCF next Attachments: manifold-elasticsearch-patch, manifold-elasticsearch-patch, manifoldcf-elasticsearch-project-patct Original Estimate: 120h Remaining Estimate: 120h An ElasticSearch connector could be very useful to spread the use of ManifoldCF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-402) Separate the proprietary / non-proprietary deliverables for each connector
[ https://issues.apache.org/jira/browse/CONNECTORS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13205132#comment-13205132 ] Karl Wright commented on CONNECTORS-402: The code in the branch is complete; just the documentation needs updating. I'll try and tackle that tomorrow. Separate the proprietary / non-proprietary deliverables for each connector -- Key: CONNECTORS-402 URL: https://issues.apache.org/jira/browse/CONNECTORS-402 Project: ManifoldCF Issue Type: Improvement Components: Build Affects Versions: ManifoldCF 0.4 Reporter: Piergiorgio Lucidi Assignee: Karl Wright Fix For: ManifoldCF 0.5 Original Estimate: 24h Remaining Estimate: 24h As we have spoken today this ticket is dedicated to try to work on the build process to separate proprietary and non-proprietary libraries in the release package. In this way, for example, we could have a standard way to release a specific library for the connector (mcf-alfresco-connector) without release proprietary libraries and allow users to add proprietary libraries in a specific folder connector-lib-proprietary that could be added to the ManifoldCF classloader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
