[jira] [Commented] (CONNECTORS-1695) Sitemap xml not detected in version 2.17 webconnector

2022-01-25 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481863#comment-17481863
 ] 

DK commented on CONNECTORS-1695:


In that case, What is the significance of 'interestingMimeType". As per the 
defect related to application/xml, it was missing in that variable and got 
added.

My understanding is that web connector would treat as special sitemap and pull 
individual urls and submit html to solr for indexing.

If that is the not case, Can we say manifoldcf does not support sitemap 
indexing? and what does it take to add the support? I am willing to help.

> Sitemap xml not detected in version 2.17 webconnector
> -
>
> Key: CONNECTORS-1695
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1695
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Web connector
>Affects Versions: ManifoldCF 2.17
>Reporter: DK
>Priority: Major
>
> Trying to index sitemap xml and web connector index the whole xml into solr.
> Please fix in version 2.17.
> If it is any special config that needs to be taken care, please add here and 
> add in documentation to make it clear.
>  
> Sitemap.xml:
> http://www.sitemaps.org/schemas/sitemap/0.9;>
> 
> https:///sitemap_1.xml
> 2022-01-21T16:04:45Z
> 
> 
>  
> sitemap_1.xml:
> 
> 
> https://
> 2018-10-31T11:25:27Z
> 
> 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (CONNECTORS-1695) Sitemap xml not detected in version 2.17 webconnector

2022-01-24 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481393#comment-17481393
 ] 

DK commented on CONNECTORS-1695:


Server returns valid sitemap xml and with mime type text/xml as mime type. As 
per another defect, it is in 'interestingMimeType' and should be supported. I 
also exclude it in solr output connector. But, I just get an error in job 
history indicating text/xml is restricted and web connector is still trying to 
process sitemap.xm as one full xml file.

Appreciate any pointers or help fixing it.

> Sitemap xml not detected in version 2.17 webconnector
> -
>
> Key: CONNECTORS-1695
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1695
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Web connector
>Affects Versions: ManifoldCF 2.17
>Reporter: DK
>Priority: Major
>
> Trying to index sitemap xml and web connector index the whole xml into solr.
> Please fix in version 2.17.
> If it is any special config that needs to be taken care, please add here and 
> add in documentation to make it clear.
>  
> Sitemap.xml:
> http://www.sitemaps.org/schemas/sitemap/0.9;>
> 
> https:///sitemap_1.xml
> 2022-01-21T16:04:45Z
> 
> 
>  
> sitemap_1.xml:
> 
> 
> https://
> 2018-10-31T11:25:27Z
> 
> 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (CONNECTORS-1695) Sitemap xml not detected in version 2.17 webconnector

2022-01-24 Thread DK (Jira) 


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DK updated CONNECTORS-1695:
---
Summary: Sitemap xml not detected in version 2.17 webconnector  (was: 
Sitemap xml not detected in version 2.17)

> Sitemap xml not detected in version 2.17 webconnector
> -
>
> Key: CONNECTORS-1695
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1695
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Web connector
>Affects Versions: ManifoldCF 2.17
>Reporter: DK
>Priority: Major
>
> Trying to index sitemap xml and web connector index the whole xml into solr.
> Please fix in version 2.17.
> If it is any special config that needs to be taken care, please add here and 
> add in documentation to make it clear.
>  
> Sitemap.xml:
> http://www.sitemaps.org/schemas/sitemap/0.9;>
> 
> https:///sitemap_1.xml
> 2022-01-21T16:04:45Z
> 
> 
>  
> sitemap_1.xml:
> 
> 
> https://
> 2018-10-31T11:25:27Z
> 
> 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (CONNECTORS-1695) Sitemap xml not detected in version 2.17

2022-01-24 Thread DK (Jira) 
DK created CONNECTORS-1695:
--

 Summary: Sitemap xml not detected in version 2.17
 Key: CONNECTORS-1695
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1695
 Project: ManifoldCF
  Issue Type: Bug
  Components: Web connector
Affects Versions: ManifoldCF 2.17
Reporter: DK


Trying to index sitemap xml and web connector index the whole xml into solr.

Please fix in version 2.17.

If it is any special config that needs to be taken care, please add here and 
add in documentation to make it clear.

 

Sitemap.xml:

http://www.sitemaps.org/schemas/sitemap/0.9;>

https:///sitemap_1.xml
2022-01-21T16:04:45Z




 

sitemap_1.xml:



https://
2018-10-31T11:25:27Z





--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (CONNECTORS-1620) Accept Sitemaps with content type application/xml

2022-01-21 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480352#comment-17480352
 ] 

DK commented on CONNECTORS-1620:


I tested this and webcrawler connector does not seem to recognize sitemap.xml 
for mimetypes text/xml and application/xml. Version 2.17. Any specifics need to 
be consider in configuring the repo or job with solr output connector?

Thanks

> Accept Sitemaps with content type application/xml
> -
>
> Key: CONNECTORS-1620
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1620
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Web connector
>Reporter: Markus Schuch
>Assignee: Markus Schuch
>Priority: Major
> Fix For: ManifoldCF 2.14
>
>
> Given an Output Connection, that does not accepts the MIME type 
> {{application/xml}} for ingestion, it is currently not possible to crawl a 
> sitemap.xml, when the webserver returns {{application/xml}} as content type 
> for the sitemap.
> The sitemap is discarded before the links are extracted, because the mime 
> type {{application/xml}} is not listed in the {{interestingMimeTypeArray}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Comment Edited] (CONNECTORS-1604) Documentation to run Manifold over SSL

2022-01-21 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830499#comment-16830499
 ] 

DK edited comment on CONNECTORS-1604 at 1/22/22, 6:32 AM:
--

Hi Karl,
Not only UI, mcf-authority-service as well.
I tried to follow documentation at
[https://www.eclipse.org/jetty/documentation/9.2.22.v20170531/configuring-ssl.html]
since
manifold runs on 9.2.x.
But, since start.jar under manifold example directory(and in other
directory) runs ManifoldJettyRunner , it does not respect start.ini etc
which specifies to load jetty-ssl.xml and jetty-https.xml. Basically, I
could not load ssl related jetty config file with manifoldcf start.jar
>From jetty doc:

The generated SSL certificates held in the key store are configured on
Jetty by injection an instance of SslContextFactory
<[http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/util/ssl/SslContextFactory.html]>
object
and passing it to the connector's SslConnectionFactory, which is done in
the jetty distribution by both in jetty-https.xml
<[http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/plain/jetty-server/src/main/config/etc/jetty-https.xml]>
and jetty-spdy.xml
<[http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/plain/jetty-spdy/spdy-example-webapp/src/main/config/etc/jetty-spdy.xml]>.
Since SPDY is able to handle HTTPS also, typically you will configure jetty
to use one of these configuration files or the other, which can be done
other on the command line or by editing the start.ini file.
Thanks

 


was (Author: durai-jira):
Hi Karl,
Not only UI, mcf-authority-service as well.
I tried to follow documentation at
https://www.eclipse.org/jetty/documentation/9.2.22.v20170531/configuring-ssl.html
since
manifold runs on 9.2.x.
But, since start.jar under manifold example directory(and in other
directory) runs ManifoldJettyRunner , it does not respect start.ini etc
which specifies to load jetty-ssl.xml and jetty-https.xml. Basically, I
could not load ssl related jetty config file with manifoldcf start.jar
>From jetty doc:

The generated SSL certificates held in the key store are configured on
Jetty by injection an instance of SslContextFactory

object
and passing it to the connector's SslConnectionFactory, which is done in
the jetty distribution by both in jetty-https.xml

 and jetty-spdy.xml
.
Since SPDY is able to handle HTTPS also, typically you will configure jetty
to use one of these configuration files or the other, which can be done
other on the command line or by editing the start.ini file.
Thanks




-- 
*Durai Kalaiselvan*
Founder, Cumilisys LLC
Office: 408 940-5135 Mobile: 408 835 0309



This email and (any accompanying attachments) may contain confidential
information belonging to the sender which is legally protected. The
information is intended only for the use of the individual or entity to
whom it is addressed, and others who have been specifically authorized by
the addressee to receive it. If you are not an intended recipient, you are
hereby notified that any disclosure, copying, or distribution of, or the
taking of any action in reliance on, this communication or the information
contained herein is strictly prohibited. If you have received this
communication in error, please notify us immediately by email or telephone.
Thank you for your cooperation.


> Documentation to run Manifold over SSL
> --
>
> Key: CONNECTORS-1604
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1604
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: DK
>Priority: Major
>
> Documentation does not talk about running manifold over SSL anywhere. I am 
> sure lot of users who deployed manifold in prod configured ssl. I tried to 
> configure SSL without success. Can someone point me to instructions to run 
> manifold over SSL please?
> Thanks



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (CONNECTORS-1629) Support Solr Kerberos Authentication

2020-09-24 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17201582#comment-17201582
 ] 

DK commented on CONNECTORS-1629:


[~kwri...@metacarta.com] / [~jornfranke] ,

Did the build change required to copt jetty-client jar make it to 2.16 and 2.17?

It looks like pre-built binaries fro 2.16 and 2.17 are missing this file in 
connector lib and we are not able to talk to solr via kerberos.

 

Please advise.

 

> Support Solr Kerberos Authentication
> 
>
> Key: CONNECTORS-1629
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1629
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: Lucene/SOLR connector
>Affects Versions: ManifoldCF 2.14
>Reporter: Jörn Franke
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.16
>
>
> Several enterprise deployments of Solr are leveraging SolrCloud Kerberos 
> authentication.
> The integration seems to be rather simple and the goal of this Jira is to 
> evaluate the possential needed step to eventually contribute the Kerberos 
> integration to the ManifoldCF project.
> The following steps would be needed:
>  * One can pass the JVM parameter java.security.auth.login.config to the 
> ManifoldCF JVM using -Djava.security.auth.login.config=/path/to/jaas.confg in 
> which Kerberos authentication details, such as keytab and principal that has 
> the right access to Solr is configured
>  * A small adaption to the SolrCloudClient that is used within Manifold needs 
> to be done to enable Kerberos authentication: 
> HttpClientUtil.setConfigurer(new Krb5HttpClientConfigurer());
> Should this be integrated in Manifold, one may want to consider one input 
> field in the configuration in the UI where one can select / flow which user 
> defined in the Jaas conf (you can define multiple one) should be chosen. By 
> default one may simply select "client" or "SolrJClient" if Jaas.conf is 
> present in the System properties. This does not mean the user needs to be 
> named like this, but the configuration entry referencing any user should be 
> named like this.
> Having a confiugration allows to have a different users per flow. This might 
> also be needed in case you have multiple Solr clusters. 
> Related discussion 
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-user/201912.mbox/browser]
> SolrJ Kerberos integration: 
> [https://lucene.apache.org/solr/guide/8_3/kerberos-authentication-plugin.html#using-solrj-with-a-kerberized-solr]
> Jaas conf documentation: 
> [https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/LoginConfigFile.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CONNECTORS-1652) ManifoldCF 2.16 docuemntation link broken

2020-09-17 Thread DK (Jira) 
DK created CONNECTORS-1652:
--

 Summary: ManifoldCF 2.16 docuemntation link broken
 Key: CONNECTORS-1652
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1652
 Project: ManifoldCF
  Issue Type: Bug
Affects Versions: ManifoldCF 2.16
Reporter: DK
 Fix For: ManifoldCF 2.16


Documentation link published is broken for 2.16

[https://manifoldcf.apache.org/release/release-2.16/en_US/index.html]

 

throws 404 - Not found



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2020-09-17 Thread DK (Jira) 


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DK updated CONNECTORS-1648:
---
Attachment: image-2020-09-17-11-42-02-988.png

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.17
>
> Attachments: image-2020-09-17-11-42-02-988.png
>
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2020-09-17 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197899#comment-17197899
 ] 

DK commented on CONNECTORS-1648:


[~kwri...@metacarta.com]

When can we expect 2.17 to be released? I see 30/08/2020 as the release date.

Is it expected to be released by this month?

!image-2020-09-17-11-42-02-988.png!

Thanks

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.17
>
> Attachments: image-2020-09-17-11-42-02-988.png
>
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2020-09-08 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17192290#comment-17192290
 ] 

DK commented on CONNECTORS-1648:


Hi [~kwri...@metacarta.com],

Switched to 2.16 and facing the same issue while connecting to Postgresql 
12.4.(Trying 12.3 for now since we are not able to find the right download for 
12.3).

Any patches or something else we should try?

Thanks

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.17
>
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2020-09-04 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190753#comment-17190753
 ] 

DK commented on CONNECTORS-1648:


getting this error from initialize script:
org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database exception: 
SQLException doing query (42703): ERROR: column pg_attrdef.adsrc does not exist
  Position: 447
    at 
org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.finishUp(Database.java:715)
    at 
org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:741)
    at 
org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Database.java:803)
    at 
org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.create(Database.java:1457)
    at 
org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:146)
    at 
org.apache.manifoldcf.core.database.Database.executeQuery(Database.java:204)
    at 
org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.performQuery(DBInterfacePostgreSQL.java:837)
    at 
org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.getTableSchema(DBInterfacePostgreSQL.java:696)
    at 
org.apache.manifoldcf.core.database.BaseTable.getTableSchema(BaseTable.java:185)
    at 
org.apache.manifoldcf.agents.agentmanager.AgentManager.install(AgentManager.java:67)
    at 
org.apache.manifoldcf.agents.system.ManifoldCF.installTables(ManifoldCF.java:112)
    at 
org.apache.manifoldcf.crawler.InitializeAndRegister.doExecute(InitializeAndRegister.java:39)
    at 
org.apache.manifoldcf.crawler.InitializeAndRegister.main(InitializeAndRegister.java:60)
Caused by: org.postgresql.util.PSQLException: ERROR: column pg_attrdef.adsrc 
does not exist
  Position: 447
    at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2476)
    at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2189)
    at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:300)
    at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:428)
    at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:354)
    at 
org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:169)
    at 
org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:117)
    at 
org.apache.manifoldcf.core.database.Database.execute(Database.java:902)
    at 
org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:696)

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.17
>
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2020-09-04 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190726#comment-17190726
 ] 

DK commented on CONNECTORS-1648:


Hi [~kwri...@metacarta.com] , Is there any pointers regarding postgres 12.3 
compatibility?

Thanks

 

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.17
>
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2020-08-24 Thread DK (Jira) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183552#comment-17183552
 ] 

DK commented on CONNECTORS-1648:


[~michaelcizmar] Did you get a chance to run performance test? Could you advise 
on compatibility, results and versions used?

[~kwri...@metacarta.com] Should we use the same postgres jdbc driver or  need 
to upgrade?

We are using Manifold 2.11. Would like to understand if manifold version needs 
to be upgraded as well to support PG 12.3 if there is no issue in performance 
tests.

 

Thanks

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.17
>
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

2020-07-06 Thread DK (Jira) 


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

DK updated CONNECTORS-1648:
---
Summary: PostgreSQL 10,11 and 12 support  (was: PostgreSQL 10,11 anad 12 
support)

> PostgreSQL 10,11 and 12 support
> ---
>
> Key: CONNECTORS-1648
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1648
> Project: ManifoldCF
>  Issue Type: Improvement
>Affects Versions: ManifoldCF 2.11, ManifoldCF 2.12, ManifoldCF 2.13, 
> ManifoldCF 2.14, ManifoldCF 2.15, ManifoldCF 2.16
>Reporter: DK
>Priority: Major
>
> As per the current documentation, "ManifoldCF has been tested against version 
> 8.3.7, 8.4.5 and 9.1 of PostgreSQL. "
> 9.1 release date is Sep 12 , 2011 and EOL on Oct 27 2016 already.
> No support for newer versions.
> This is important to deploy ManifoldCF in an enterprise environment where 
> value added service such as HA, Backup and Recovery and Monitoring etc are 
> provided by third party vendors. These vendors do not support postgreSql 
> versions which are reaching end of life.
> Any plan to test and certify recent versions such as 10,11 and 12.3?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)