[jira] [Commented] (CONNECTORS-1492) GSOC: Add support for Docker

[ https://issues.apache.org/jira/browse/CONNECTORS-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246574#comment-17246574 ] Michael Cizmar commented on CONNECTORS-1492: We've been using Docker Compose

[jira] [Commented] (CONNECTORS-1659) Enable SSL/TLS in Jetty server

[ https://issues.apache.org/jira/browse/CONNECTORS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17237830#comment-17237830 ] Michael Cizmar commented on CONNECTORS-1659: If the Jetty server are starting up without

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

20 at 9:28 PM Karl Wright wrote: > > > >> I used a -D variable that is set differently by maven and ant builds. > >> > >> It works fine for ant. Bandwidth limitations tonight mean I will try > >> tomorrow morning for maven. > >> > >> Karl &

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

during testing; the ant > test explicitly sets it to one of the build directories below that. But in > any case I will need to consider how the test can be changed to use a > specific ES source directory; maybe a -D can be pushed into it. > > Karl > > On Sat, Sep 12, 202

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

t.println("Windows process"); } + + File log = new File("es.log"); pb.redirectErrorStream(true); pb.redirectOutput(ProcessBuilder.Redirect.appendTo(log)); esTestProcess = pb.start(); + System.out.println("ElasticSearch is starting...");

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Didn't reach ES; waiting... Didn't reach ES; waiting... Didn't reach ES; waiting... Response from ES: HTTP/1.1 200 OK ES came up! ElasticSearch is started on port 9200 @Karl - How would you like this packaged up? On Sat, Sep 12, 2020 at 12:52 PM Michael Cizmar wrote: > Agreed. We w

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

> see if there is a way to do that. > Karl > > > On Sat, Sep 12, 2020 at 12:00 PM Michael Cizmar > > wrote: > > > I think you are right. The es.log file contains the following: > > > > bash: ../test-materials/unix/elasticsearch-7.6.2/bin/elasticsearch: No > such >

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

/elasticsearch: No such file or directory On Sat, Sep 12, 2020 at 10:49 AM Karl Wright wrote: > Ok, I didn't realize this was from Maven only. It may be a working > directory or dependency version issue. > > > On Sat, Sep 12, 2020 at 11:37 AM Michael Cizmar > > wrote: > >

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

I reproduced the infinite Elastic Search Loop when building from maven. I'm investigating it now. On Sat, Sep 12, 2020 at 9:30 AM Michael Cizmar wrote: > I'll take a look at the build this AM. > > On Sat, Sep 12, 2020 at 5:13 AM Karl Wright wrote: > >> Hi all, >> &

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

ng... > > Didn't reach ES; waiting... > > Didn't reach ES; waiting... > > Didn't reach ES; waiting... > > Didn't reach ES; waiting... > > Didn't reach ES; waiting... > > Didn't reach ES; waiting... > > Didn't reach ES; waiting... > > Didn't reach ES; waitin

Re: [VOTE] Release Apache ManifoldCF 2.17, RC1

Cihad, What was the error that you received when compiling in maven? On Wed, Sep 9, 2020 at 3:39 AM Cihad Guzel wrote: > Hi Karl, > > I have successfully compiled using ant build. I tried to compile the tag[1] > using maven, but the ElasticSearch tests still fail using Mac [2] . >

[jira] [Commented] (CONNECTORS-1651) ElasticSearch server is not starting during integration test

[ https://issues.apache.org/jira/browse/CONNECTORS-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17188934#comment-17188934 ] Michael Cizmar commented on CONNECTORS-1651: I do not particularly like how Elastic

Re: [VOTE] Release Apache ManifoldCF 2.17, RC0

>From what I see it does not appear that the tests are failing. The Elastic search container is not starting. I agree with Karl. On Sat, Aug 29, 2020 at 9:24 AM Karl Wright wrote: > Hmm, the way it starts the process is the same on Windows and Linux. The > version of ES we download for the

Re: Document Splitter

Cool. I'll shift to that approach. Have a lot of cases were we are indexing a csv, xml, or json file where we want them split up. -- Michael Cizmar Managing Director p: 312.585.6396 d: 312.585.6286 twitter: @michaelcizmar<http://twitter.com/michaelcizmar> http://www.mcplu

Re: Document Splitter

Michael Cizmar wrote: > I have a Json file which has an array of objects that I want to index > as separate documents. Before I build a transformer to split it, is > there a ready made transformer to do this? > > Thanks! > > Michael >

[jira] [Commented] (CONNECTORS-1648) PostgreSQL 10,11 and 12 support

[ https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153142#comment-17153142 ] Michael Cizmar commented on CONNECTORS-1648: No.  I can give that a go in the next week

Document Splitter

I have a Json file which has an array of objects that I want to index as separate documents. Before I build a transformer to split it, is there a ready made transformer to do this? Thanks! Michael

[jira] [Commented] (CONNECTORS-1648) PostgreSQL 10,11 and 12 support

[ https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152340#comment-17152340 ] Michael Cizmar commented on CONNECTORS-1648: It works with new versions.  I think we've

[jira] [Commented] (CONNECTORS-1642) PostgreSQL Version >= 12.2 DB Initialization Problems

[ https://issues.apache.org/jira/browse/CONNECTORS-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105371#comment-17105371 ] Michael Cizmar commented on CONNECTORS-1642: Is sort of a latest version issue?  We got

Re: MongoDB download now no longer works

load still: https://repo1.maven.org/maven2/de/flapdoodle/embed/de.flapdoodle.embed.mongo/2.2.0/ -- Michael Cizmar On 5/5/20, 8:55 AM, "Karl Wright" wrote: A unit test for the MongoDB connector needs to download a version of MongoDB to do this testing. Unfortunately it lo

Re: [VOTE] Release Apache ManifoldCF 2.16, RC0

Great work Karl! I'm looking forward to trying this out. On Sun, May 3, 2020 at 1:31 PM Karl Wright wrote: > Please vote on whether to release Apache ManifoldCF 2.16, RC0. This > release has a new confluence connector as well as preliminary support for > Java 11. The release artifact can be

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097963#comment-17097963 ] Michael Cizmar commented on CONNECTORS-1639: [~kwri...@metacarta.com] I modified

[jira] [Updated] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Cizmar updated CONNECTORS-1639: --- Attachment: es_start.sh > Upgrade Elastic Search Vers

[jira] [Updated] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Cizmar updated CONNECTORS-1639: --- Attachment: (was: es_start.sh) > Upgrade Elastic Search Vers

[jira] [Updated] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Cizmar updated CONNECTORS-1639: --- Attachment: es_start.sh > Upgrade Elastic Search Vers

[jira] [Updated] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Cizmar updated CONNECTORS-1639: --- Attachment: es_stop.sh > Upgrade Elastic Search Vers

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097747#comment-17097747 ] Michael Cizmar commented on CONNECTORS-1639: This should spin up the instance

Re: Should we continue to hold the 4/30 release until the ES testing is ironed out?

Karl, We created the script for you today and added it to: https://issues.apache.org/jira/browse/CONNECTORS-1639 I had them make one to start it up and one to shut it down. Please let me know if this works for you. -- Michael Cizmar On 5/1/20, 6:02 AM, "Karl Wright" wrote:

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097658#comment-17097658 ] Michael Cizmar commented on CONNECTORS-1639: [^es_start.sh] ^[^es_stop.sh]^ ^Attached

Re: Should we continue to hold the 4/30 release until the ES testing is ironed out?

Karl. We'll get you this script today. Been slammed with end of month stuff. Sorry for the delay. On 5/1/20, 6:02 AM, "Karl Wright" wrote: I've got time this weekend to make code changes, but I don't actually know how to proceed, so I think we're stuck. What I need to have is

Re: Status of Elastic Search integration tests

transmission to ES, and ES obviously needs to handle those for the > integration to work properly. > > Karl > > > On Wed, Apr 29, 2020 at 7:27 AM Michael Cizmar > wrote: > > > There's been some changes to Elasticsearch like reducing the document > types > &g

Re: Status of Elastic Search integration tests

There's been some changes to Elasticsearch like reducing the document types and ingestion/mapper. The mapper attachment I believe has been deprecated in favor of: https://www.elastic.co/guide/en/elasticsearch/plugins/master/ingest-attachment.html This should be incorporated into a pipeline. Do

Re: Release schedule

to shut ES down via a similar HTTP Get mechanism. > > Can you verify that waiting for ES to come up and shutting down ES can be > done with the same mechanism as is currently in the test code? > > Karl > > > On Thu, Apr 23, 2020 at 7:44 AM Michael Cizmar > wrote: &

Re: Release schedule

; Karl > > > On Sat, Apr 18, 2020 at 5:52 PM Michael Cizmar > wrote: > > > I've updated the ticket with the changes: > > > > > https://issues.apache.org/jira/projects/CONNECTORS/issues/CONNECTORS-1639 > > > > On Sat, Apr 18, 2020 at 3:59 PM Cihad

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087254#comment-17087254 ] Michael Cizmar commented on CONNECTORS-1639: Was away from my desk, the setup script

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086677#comment-17086677 ] Michael Cizmar commented on CONNECTORS-1639: Right.  If you upgrade/remove the library

Re: Release schedule

I can help with Ant tasks but I need information as to how you're > supposed > > to start the ES instance. An ant task snippet would be sufficient I > think. > > > > > > On Sat, Apr 18, 2020 at 10:33 AM Michael Cizmar < > > michael.ciz...@mcplusa.com&g

[jira] [Updated] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Cizmar updated CONNECTORS-1639: --- Attachment: CONNECTORS-1639.diff > Upgrade Elastic Search Vers

Re: Release schedule

: Karl Wright Sent: Saturday, April 18, 2020 9:15:15 AM To: dev Subject: Re: Release schedule Hi Michael, This has to run under Ant as well. Any way to make that happen? Karl On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar wrote: > I've got a fix for this. I switched to using a Maven plugin t

Re: Release schedule

versions and Java 11. I’ll clean up what I worked on and submitted it for consideration. Michael From: Furkan KAMACI Date: Saturday, April 18, 2020 at 9:04 AM To: Michael Cizmar Cc: "dev@manifoldcf.apache.org" Subject: Re: Release schedule Hi, By the way, when I check the error he

Re: Release schedule

I've got a fix for this. I switched to using a Maven plugin that spins up an Elasticsearch instance. With this, you need only to remove the Node code in the integration tests. Tested with 6.x client and 7.x elasticsearch. There are more things we can do with this output plugin in the future

Re: Release schedule

Right. The issue is that the unit tests rely on embedding an elasticsearch instance which is officially deprecated: https://www.elastic.co/blog/elasticsearch-the-server There are integration methods using ESIntegTestCase. I'm looking if we can quickly refactor to utilize that or the unit

[jira] [Comment Edited] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064416#comment-17064416 ] Michael Cizmar edited comment on CONNECTORS-1639 at 3/22/20, 8:53 PM

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064416#comment-17064416 ] Michael Cizmar commented on CONNECTORS-1639: The output connector uses is 1.0.1

Re: ElasticSearch-literate volunteers needed for JDK 11 port

We can take a look. Get Outlook for iOS From: Karl Wright Sent: Sunday, March 22, 2020 10:05:40 AM To: dev Subject: ElasticSearch-literate volunteers needed for JDK 11 port Hi All, The version of ElasticSearch we support apparently is

java.net.SocketException: Socket is closed

Wondering if anyone else has seen this when configuring a forms authentication rule via Access Credentials. When the post to the form is made...it times out and returns the exception below. The form looks corrected. Thanks, M - DEBUG 2020-03-16T21:05:48,423 (Thread-7314) - Connection

[jira] [Commented] (CONNECTORS-1633) Exception tossed: Repeated service interruptions - failure processing document: The process cannot access the file because it is being used by another process.

[ https://issues.apache.org/jira/browse/CONNECTORS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023000#comment-17023000 ] Michael Cizmar commented on CONNECTORS-1633: I don't think the whole job should

[jira] [Created] (CONNECTORS-1633) Exception tossed: Repeated service interruptions - failure processing document: The process cannot access the file because it is being used by another process.

Michael Cizmar created CONNECTORS-1633: -- Summary: Exception tossed: Repeated service interruptions - failure processing document: The process cannot access the file because it is being used by another process. Key

[jira] [Commented] (CONNECTORS-1608) Connecting ADFS user using SharePoint Connector

[ https://issues.apache.org/jira/browse/CONNECTORS-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022934#comment-17022934 ] Michael Cizmar commented on CONNECTORS-1608: ADFS makes some additional redirects.  You

[jira] [Created] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

Michael Cizmar created CONNECTORS-1619: -- Summary: When you edit the Elastic Output connector, you need to set the password again Key: CONNECTORS-1619 URL: https://issues.apache.org/jira/browse/CONNECTORS

Re: ManifoldCF Resource Offering

ns of The Book. You can see them for free here: > > https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs > > Karl > > > On Fri, Aug 16, 2019 at 8:33 AM Michael Cizmar > wrote: > > > For better or worse, my company (MC+A <https://www.mcplusa.com/>)

Re: Unexpected HTTP result code: -1: null

Priya - Was this right? 48GB and 1-Core Intel(R) Xeon(R) CPU While not directly related to an out of memory issue, you should have more cores allocated to ES. On Fri, Aug 16, 2019 at 1:09 AM Priya Arora wrote: > *Existing Threads/connections configuration is :-* > > How many worker threads

Re: ManifoldCF Resource Offering

; yazdı: > > > Excellent! > > Thanks for contacting us. I hope we can help. > > > > Karl > > > > On Thu, Aug 15, 2019 at 9:17 PM Michael Cizmar < > mich...@michaelcizmar.com> > > wrote: > > > > > Hey Folks, > > > &

ManifoldCF Resource Offering

Hey Folks, I exchanged emails with Karl earlier this week, but I wanted to reach out to you to offer up some additional assistance for the ManifoldCF project. My firm has previously written about a dozen commercial connectors primarily targeted to the Google Search Appliance. We are starting to

Re: Reminder: August 31st is the next scheduled ManifoldCF release

I think it's good to be on a cadence to release regardless of the amount changed. Additionally, the release of the Elastic output connector is compelling. On Mon, Aug 12, 2019 at 7:57 AM Karl Wright wrote: > I had hoped that we could finish the OpenText Content Service/Web Service > connector

Re: Elastic Output Connector SSLException

Update on this. I increased the output connections from 10 to 20 and removed the enablement of security on the repository and the issue has not been repeated. On Fri, Aug 9, 2019 at 10:23 AM Michael Cizmar wrote: > Right. Specifically, this is occurring where the output connector > at

Re: Elastic Output Connector SSLException

l use them if that is what is negotiated. This is going to require more debugging help than this list can probably provide. Karl On Fri, Aug 9, 2019 at 9:26 AM Michael Cizmar wrote: > Curious if anyone has received this a connection exception on the elastic > output connector and/or had an i

Elastic Output Connector SSLException

Curious if anyone has received this a connection exception on the elastic output connector and/or had an idea for the root cause. Thanks, Michael org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[httpclient-4.5.6.jar:4.5.6] at

[jira] [Commented] (CONNECTORS-1615) Bad Error Message when IDCOLUMN's value is actually null

[ https://issues.apache.org/jira/browse/CONNECTORS-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897375#comment-16897375 ] Michael Cizmar commented on CONNECTORS-1615: Roger that.  Please forgive my ignorance

[jira] [Commented] (CONNECTORS-1615) Bad Error Message when IDCOLUMN's value is actually null

[ https://issues.apache.org/jira/browse/CONNECTORS-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897370#comment-16897370 ] Michael Cizmar commented on CONNECTORS-1615: Which doesn't explain why the logging can't

[jira] [Commented] (CONNECTORS-1615) Bad Error Message when IDCOLUMN's value is actually null

[ https://issues.apache.org/jira/browse/CONNECTORS-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897158#comment-16897158 ] Michael Cizmar commented on CONNECTORS-1615: Right.   However, the case

[jira] [Created] (CONNECTORS-1615) Bad Error Message when IDCOLUMN's value is actually null

Michael Cizmar created CONNECTORS-1615: -- Summary: Bad Error Message when IDCOLUMN's value is actually null Key: CONNECTORS-1615 URL: https://issues.apache.org/jira/browse/CONNECTORS-1615 Project

[jira] [Commented] (CONNECTORS-1519) CLIENTPROTOCOLEXCEPTION is thrown with 2.10 -> ES 6.x.y

[ https://issues.apache.org/jira/browse/CONNECTORS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871075#comment-16871075 ] Michael Cizmar commented on CONNECTORS-1519: Cool.  Using something like Pre-emptive