[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[James Thomas (JIRA)]

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

James Thomas commented on CONNECTORS-1521:
--

Another potential approach: is it possible to request the time of the DM server 
(or perhaps parse it out of responses to other requests, as in HTTP headers?) 
and use that in the DQL instead of local time?

> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Mon Oct 29 00:01:13 CET 2018
> r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
> {noformat}
> But if I set the time inside DST, the time is an hour before:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Sat Oct 27 00:00:06 CEST 2018
> r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 
> {noformat}
> This is perhaps a Java issue rather than a logic issue in the connector? See 
> e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1490:
-

The only remaining issue is how the tests are run.  They should be invoked 
directly using the ant build, not shelled out using Maven.

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mcf-mongodb-connector(CONNECTORS-1490)1.patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1490:
-

ok, moved.


> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mcf-mongodb-connector(CONNECTORS-1490)1.patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela updated CONNECTORS-1490:

Comment: was deleted

(was: [^mcf-mongodb-connector(CONNECTORS-1490)1.patch]

 )

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mcf-mongodb-connector(CONNECTORS-1490)1.patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela updated CONNECTORS-1490:

Attachment: mcf-mongodb-connector(CONNECTORS-1490)1.patch

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mcf-mongodb-connector(CONNECTORS-1490)1.patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela commented on CONNECTORS-1490:
-

Hi Karl,

I am really sorry I made a small mistake after applying the last patch the 
folder src under manifoldcf/connectors/mongodb should be moved to a folder 
named connectors made under manifoldcf/connectors/mongodb which is the 
equivalent of 

cd manifoldcf/connectors/mongodb

mkdir connectors

mv ./src ./connectors

I have also made the correct patch 
[mcf-mongodb-connector(CONNECTORS-1490)1.patch] without the mistake please use 
it if it is more convenient to you  and also note you still need to manually 
copy the image attached before even with new patch named 
mcf-mongodb-connector(CONNECTORS-1490)1.patch

[^mcf-mongodb-connector(CONNECTORS-1490)1.patch]

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela commented on CONNECTORS-1490:
-

[^mcf-mongodb-connector(CONNECTORS-1490)1.patch]

 

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[James Thomas (JIRA)]

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

James Thomas commented on CONNECTORS-1521:
--

No, there's no patterns with "Z"

> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Mon Oct 29 00:01:13 CET 2018
> r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
> {noformat}
> But if I set the time inside DST, the time is an hour before:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Sat Oct 27 00:00:06 CEST 2018
> r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 
> {noformat}
> This is perhaps a Java issue rather than a logic issue in the connector? See 
> e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela commented on CONNECTORS-1490:
-

Hi Karl,

The connector as of now depends on mongo-java-driver 2.11.3 which is a common 
dependency for the GridFS repository connector as well

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1490:
-

I have committed the patch and the PNG file to branches/CONNECTORS-1490.


> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1490:
-

Also, build.xml has the following:

{code}



























{code}

This is leveraging (and requiring!) a maven setup to run the actual IT tests 
for this connector.  That's not something we can support, since the ant build 
is primary here.


> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1490:
-

What was the final decision about what version of the jar that this connector 
should depend upon?


> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela updated CONNECTORS-1490:

Attachment: mcf-mongodb-connector(CONNECTORS-1490).patch

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela updated CONNECTORS-1490:

Attachment: mongodb-output-connection-configuration.PNG

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mcf-mongodb-connector(CONNECTORS-1490).patch, 
> mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela commented on CONNECTORS-1490:
-

!mongodb-output-connection-configuration.PNG![^mcf-mongodb-connector(CONNECTORS-1490).patch]

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
> Attachments: mongodb-output-connection-configuration.PNG
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela edited comment on CONNECTORS-1490 at 8/7/18 2:05 PM:
-

Attaching the patch for MongoDB Output Connector 

please note that the image file mongodb-output-connection-configuration.PNG at 
manifoldcf\site\src\documentation\resources\images\en_US is not generated with 
the patch and please be kind to copy that manually I am attaching the 
mongodb-output-connection-configuration.PNG file along with the patch.

Also note that the patch can be applied fine with Eclispe IDE and I faced some 
problems applying the patch with Intelij IDEA It is better if it is possible to 
avoid Intelij IDEA to apply the patch

 


was (Author: irindupera):
Attaching the patch for MongoDB Output Connector 

please note that the image file mongodb-output-connection-configuration.PNG at 
manifoldcf\site\src\documentation\resources\images\en_US is not generated with 
the patch and please be kind to copy that manually I am attaching the 
mongodb-output-connection-configuration.PNG file along with the patch.

Also note that the patch can be applied fine with Eclispe IDE and I faced some 
problems applying the patch with Intelij IDEA It is better if it is possible to 
avoid Intelij IDEA to apply the patch

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1490) GSOC: MongoDB Output Connector

[Irindu Nugawela (JIRA)]

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

Irindu Nugawela commented on CONNECTORS-1490:
-

Attaching the patch for MongoDB Output Connector 

please note that the image file mongodb-output-connection-configuration.PNG at 
manifoldcf\site\src\documentation\resources\images\en_US is not generated with 
the patch and please be kind to copy that manually I am attaching the 
mongodb-output-connection-configuration.PNG file along with the patch.

Also note that the patch can be applied fine with Eclispe IDE and I faced some 
problems applying the patch with Intelij IDEA It is better if it is possible to 
avoid Intelij IDEA to apply the patch

> GSOC: MongoDB Output Connector
> --
>
> Key: CONNECTORS-1490
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1490
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: MongoDB Output Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: MongoDB, gsoc2018, java, junit
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Migration capabilities adding MongoDB / 
> GridFS as a new output connector for importing contents from one or more 
> repositories supported by ManifoldCF. In this way we will help developers on 
> migrating contents from different data sources on MongoDB.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> We have a complete documentation on how to implement an Output Connector:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/writing-output-connectors.html]
> Take a look also at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1521:
-

{quote}
As far as I can see none of the patterns gives anything related to time zone or 
locale, or mentions UTC, DST etc.
{quote}

If there's a pattern with a "Z" at the end or in the middle, that usually 
stands for "Zulu" and is UTC.  Are there any such patterns?


> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Mon Oct 29 00:01:13 CET 2018
> r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
> {noformat}
> But if I set the time inside DST, the time is an hour before:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Sat Oct 27 00:00:06 CEST 2018
> r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 
> {noformat}
> This is perhaps a Java issue rather than a logic issue in the connector? See 
> e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1521:
-

[~jamesthomas], computing a date relative to "now" is trivial but it's not 
clear how you form a DQL expression involving r_modify_date with this.

The StackOverflow article is about how to get DFC to return dates in forms that 
are parseable by C Sharp, which is not germane here either, because we want 
dates that are in a form we can use for comparison.




> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Mon Oct 29 00:01:13 CET 2018
> r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
> {noformat}
> But if I set the time inside DST, the time is an hour before:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Sat Oct 27 00:00:06 CEST 2018
> r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 
> {noformat}
> This is perhaps a Java issue rather than a logic issue in the connector? See 
> e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--
This message was sent by Atlassian JIRA

[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[James Thomas (JIRA)]

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

James Thomas commented on CONNECTORS-1521:
--

Taking a different approach, I looked for alternative time and date formats. 
Might com.documentum.fc.client.search Interface IDfRelativeDateExpression be 
interesting?
{noformat}
Defines an expression on a date that is relative to the actual date when the 
query is executed. For example, a date greater than ( - 3 months). 
The inherited method getValue() returns a dynamic date that is relative to the 
actual date when the query is executed.

{noformat}
With methods:

 
{noformat}
int getRelativeTime()
Gets the number of time units for the relative date expression.
 These time units are added to the current date to compute the real expression 
date. For example, if search operator=GREATER_THAN, relative time=-3, time 
unit=MONTH, then the expression defines a constraint on a date that must be 
greater than the current date minus 3 months. In this example, this method 
would return the value -3.
Returns:
 The number of time units for the relative date expression.
 int getTimeUnit()
Gets the time unit for the relative date expression.
 For example, if searchOpCode=GREATER_THAN, relativeTime=-3, timeUnit=MONTH, 
then the expression defines a constraint on a date that must be greater than 
the current date minus 3 months. In this example, this method would return the 
value MONTH.
Returns:
 The time unit for the relative date expression.
 
{noformat}
 

 

> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connect

Re: It's release time again

[Piergiorgio Lucidi]

It's ok for me,

I wanted to finish several things but unfortunately I will not have enough
time.
The MongoDB Output Connector implemented by Irindu will be merged in our
branch during this week but I don't know if we have time to directly bring
it in this release.

In September I hope to bring the new website and Alfresco BFSI and then the
Azure Storage connectors.

Cheers,
PJ

Il giorno mar 7 ago 2018 alle ore 14:05 Karl Wright  ha
scritto:

> When will it be ready for integration?
> Karl
>
> On Tue, Aug 7, 2018 at 7:10 AM Irindu Nugawela 
> wrote:
>
> > Hi Karl,
> >
> > I am currently preparing the patch for mcf-mongodb-output-connector. I
> > would be glad if we can include it in the next release.
> >
> > On Mon, 6 Aug 2018 at 16:00, Karl Wright  wrote:
> >
> > > I'm hoping to cut RC0 of 2.11 around August 15th. Any objection?
> > >
> > > Karl
> > >
> >
> >
> > --
> > Thanks and Regards,
> > Irindu Nugawela,
> > Computer Engineering  Undergraduate,
> > Faculty of Engineering University of Peradeniya
> >
>
> --
> Piergiorgio
>

[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[James Thomas (JIRA)]

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

James Thomas commented on CONNECTORS-1521:
--

(I am not a developer but ...) I have explored the Javadoc for 
com.documentum.fc.common, Interface IDfTime in DFC 16.4

There are ~50 patterns, here's a couple of examples:

 
{noformat}
DF_TIME_PATTERN8 Represents time pattern string "month dd, ".
DF_TIME_PATTERN34 Represents time pattern string "mon- hh:mi:ss".
{noformat}
As far as I can see none of the patterns gives anything related to time zone or 
locale, or mentions UTC, DST etc.

This is consistent with the blog post that you found.

Googling around a little, I came across these:

[https://stackoverflow.com/a/8315831] which looks related to your comment about 
asString().

[https://msroth.wordpress.com/2011/05/15/the-content-server-and-time-zones|https://msroth.wordpress.com/2011/05/15/the-content-server-and-time-zones,m]
 and [https://blog.documentum.pro/2015/02/04/time-in-documentum] which are in 
this general area.

 

> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ da

Re: It's release time again

[Karl Wright]

When will it be ready for integration?
Karl

On Tue, Aug 7, 2018 at 7:10 AM Irindu Nugawela  wrote:

> Hi Karl,
>
> I am currently preparing the patch for mcf-mongodb-output-connector. I
> would be glad if we can include it in the next release.
>
> On Mon, 6 Aug 2018 at 16:00, Karl Wright  wrote:
>
> > I'm hoping to cut RC0 of 2.11 around August 15th. Any objection?
> >
> > Karl
> >
>
>
> --
> Thanks and Regards,
> Irindu Nugawela,
> Computer Engineering  Undergraduate,
> Faculty of Engineering University of Peradeniya
>

Re: It's release time again

[Irindu Nugawela]

Hi Karl,

I am currently preparing the patch for mcf-mongodb-output-connector. I
would be glad if we can include it in the next release.

On Mon, 6 Aug 2018 at 16:00, Karl Wright  wrote:

> I'm hoping to cut RC0 of 2.11 around August 15th. Any objection?
>
> Karl
>


-- 
Thanks and Regards,
Irindu Nugawela,
Computer Engineering  Undergraduate,
Faculty of Engineering University of Peradeniya

[jira] [Comment Edited] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[Karl Wright (JIRA)]

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

Karl Wright edited comment on CONNECTORS-1521 at 8/7/18 11:05 AM:
--

All I have access to indicates that IDfTime patterns are very iffy:

https://msroth.wordpress.com/2010/12/12/dftime-patterns/

... and I don't see any sign of UTC dates or timezones.




was (Author: kwri...@metacarta.com):
All I have access to indicates that IDfTime patterns are very iffy:

https://msroth.wordpress.com/2010/12/12/dftime-patterns/



> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Mon Oct 29 00:01:13 CET 2018
> r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
> {noformat}
> But if I set the time inside DST, the time is an hour before:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Sat Oct 27 00:00:06 CEST 2018
> r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 
> {noformat}
> This is perhaps a Java issue rather than a logic issue in the connector? See 
> e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--

[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1521:
-

All I have access to indicates that IDfTime patterns are very iffy:

https://msroth.wordpress.com/2010/12/12/dftime-patterns/



> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Mon Oct 29 00:01:13 CET 2018
> r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
> {noformat}
> But if I set the time inside DST, the time is an hour before:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Sat Oct 27 00:00:06 CEST 2018
> r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 
> {noformat}
> This is perhaps a Java issue rather than a logic issue in the connector? See 
> e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1521:
-

The method that is used to build the date string is as follows:

{code}
session.buildDateString(timevalue);
{code}

... where timevalue is a time in ms since epoch.

The buildDateString code is here, in DocumentumImpl:

{code}
  /** Build a DQL date string from a long timestamp */
  public String buildDateString(long timestamp)
throws RemoteException
  {
return "date('"+new DfTime(new 
Date(timestamp)).asString(IDfTime.DF_TIME_PATTERN44)+"','"+IDfTime.DF_TIME_PATTERN44+"')";
  }
{code}

The Date object created is time-zone free (because that's the way Date objects 
work).  The asString() method probably uses local time though.

I can't change this without access to DFC documentation -- specifically, I need 
to know what DfTime formats are accepted, and if any UTC formats are 
understood, or if there are formats with timezones.  I also need the name of 
the appropriate IDfTime constant. 
 [~jamesthomas], is this something you can research?


> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> 

[jira] [Assigned] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[Karl Wright (JIRA)]

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

Karl Wright reassigned CONNECTORS-1521:
---

Assignee: Karl Wright

> Documentum Connector users ManifoldCF's local time in queries constraints 
> against the Documentum server without reference to time zones
> ---
>
> Key: CONNECTORS-1521
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Documentum connector
>Affects Versions: ManifoldCF 2.10
>Reporter: James Thomas
>Assignee: Karl Wright
>Priority: Major
>
> I find that the time/date constraints in queries to the Documentum server are 
> based on the "raw" local time of the ManifoldCF server but appear to take no 
> account of the time zones of the two servers.
> This can lead to recently modified files not being transferred to the output 
> repository when you would naturally expect them to be. I'd like the times to 
> be aligned, perhaps by including time zone in the query. In particular, is 
> there a way to use UTC perhaps?
> Here's an example ...
>  * create a folder in Documentum
>  * set up a job to point at the folder and output to the file system
>  * put two documents into a folder in Documentum
>  * Select them, right click and export as CSV (to show the timestamps):
> {noformat}
> 1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
> 2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
> Check the local time on the ManifoldCF server machine. Observe that it's 
> reporting consistent time with the DM server:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 09:07:25 BST 2018{noformat}
> Start the job and look for the query to Documentum in the manifoldcf.log file 
> (line break added for readability):
> {noformat}
> DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute 
> query= (select for READ distinct i_chronicle_id from dm_document where 
> r_modify_date >= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and
> r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 
> AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
> r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
> ^C{noformat}
> Notice that the latest date asked for is *before* the modification date of 
> the files added to DM. (And is an hour out, see footnote.)
>   
>  See whether anything has been output by the File System connector. It hasn't:
> {noformat}
> [james@manifold]$ ls /bigdisc/source/PDFs/timezones/
> [james@manifold]$
> {noformat}
> Now:
>  * change the timezone on the ManifoldCF server machine
>  * restart the ManifoldCF server and the Documentum processes
>  * reseed the job
> Check the local time on the ManifoldCF server machine; it has changed:
> {noformat}
> [james@manifold]$ date
> Tue Aug  7 10:10:29 CEST 2018{noformat}
> Start the job again and notice that the query has changed by an hour, plus 
> the few minutes it took to change the date etc (and is still an hour out, see 
> footnote):
> {noformat}
> r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
> {noformat}
> Observe that the range of dates now covers the timestamps on the DM data, and 
> also that some data has now been transferred by the File System connector:
> {noformat}
> [james@manifold]$ ls 
> /bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
> drl?versionLabel=CURRENT&objectId=09018000e515
> drl?versionLabel=CURRENT&objectId=09018000e516
> {noformat}
>  
>  
> [Footnote] It appears that something is trying to take account of Daylight 
> Saving Time too.
> If I set the server date to a time outside of DST, the query is aligned with 
> the current time:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Mon Oct 29 00:01:13 CET 2018
> r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
> {noformat}
> But if I set the time inside DST, the time is an hour before:
> {noformat}
> [i2e@i2ehost manifold]$ date
>  Sat Oct 27 00:00:06 CEST 2018
> r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 
> {noformat}
> This is perhaps a Java issue rather than a logic issue in the connector? See 
> e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[James Thomas (JIRA)]

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

James Thomas updated CONNECTORS-1521:
-
Description: 
I find that the time/date constraints in queries to the Documentum server are 
based on the "raw" local time of the ManifoldCF server but appear to take no 
account of the time zones of the two servers.

This can lead to recently modified files not being transferred to the output 
repository when you would naturally expect them to be. I'd like the times to be 
aligned, perhaps by including time zone in the query. In particular, is there a 
way to use UTC perhaps?

Here's an example ...
 * create a folder in Documentum
 * set up a job to point at the folder and output to the file system
 * put two documents into a folder in Documentum
 * Select them, right click and export as CSV (to show the timestamps):

{noformat}
1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
Check the local time on the ManifoldCF server machine. Observe that it's 
reporting consistent time with the DM server:
{noformat}
[james@manifold]$ date
Tue Aug  7 09:07:25 BST 2018{noformat}
Start the job and look for the query to Documentum in the manifoldcf.log file 
(line break added for readability):
{noformat}
DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute query= 
(select for READ distinct i_chronicle_id from dm_document where r_modify_date 
>= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and

r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 

AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
^C{noformat}
Notice that the latest date asked for is *before* the modification date of the 
files added to DM. (And is an hour out, see footnote.)
  
 See whether anything has been output by the File System connector. It hasn't:
{noformat}
[james@manifold]$ ls /bigdisc/source/PDFs/timezones/
[james@manifold]$
{noformat}
Now:
 * change the timezone on the ManifoldCF server machine
 * restart the ManifoldCF server and the Documentum processes
 * reseed the job

Check the local time on the ManifoldCF server machine; it has changed:
{noformat}
[james@manifold]$ date
Tue Aug  7 10:10:29 CEST 2018{noformat}
Start the job again and notice that the query has changed by an hour, plus the 
few minutes it took to change the date etc (and is still an hour out, see 
footnote):
{noformat}
r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
{noformat}
Observe that the range of dates now covers the timestamps on the DM data, and 
also that some data has now been transferred by the File System connector:
{noformat}
[james@manifold]$ ls 
/bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
drl?versionLabel=CURRENT&objectId=09018000e515
drl?versionLabel=CURRENT&objectId=09018000e516
{noformat}
 

 

[Footnote] It appears that something is trying to take account of Daylight 
Saving Time too.

If I set the server date to a time outside of DST, the query is aligned with 
the current time:
{noformat}
[i2e@i2ehost manifold]$ date
 Mon Oct 29 00:01:13 CET 2018

r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
{noformat}
But if I set the time inside DST, the time is an hour before:
{noformat}
[i2e@i2ehost manifold]$ date
 Sat Oct 27 00:00:06 CEST 2018

r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 

{noformat}
This is perhaps a Java issue rather than a logic issue in the connector? See 
e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]

  was:
I find that the time/date constraints in queries to the Documentum server are 
based on the "raw" local time of the ManifoldCF server but appear to take no 
account of the time zones of the two servers.

This can lead to recently modified files not being transferred to the output 
repository when you would naturally expect them to be. I'd like the times to be 
aligned, perhaps by including time zone in the query. In particular, is there a 
way to use UTC perhaps?

Here's an example ...
 * create a folder in Documentum
 * set up a job to point at the folder and output to the file system
 * put two documents into a folder in Documentum
 * Select them, right click and export as CSV (to show the timestamps):

{noformat}
1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
Check the local time on the ManifoldCF server machine. Observe that it's 
reporting consistent time with the DM server:
{noformat}
[james@manifold]$ date
Tue Aug  7 09:07:25 BST 2018{noformat}
Start the job and look for the query to Documentum in the manifoldcf.log file 
(line break added for readability):
{noformat}
DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM:

[jira] [Created] (CONNECTORS-1521) Documentum Connector users ManifoldCF's local time in queries constraints against the Documentum server without reference to time zones

[James Thomas (JIRA)]

James Thomas created CONNECTORS-1521:


 Summary: Documentum Connector users ManifoldCF's local time in 
queries constraints against the Documentum server without reference to time 
zones
 Key: CONNECTORS-1521
 URL: https://issues.apache.org/jira/browse/CONNECTORS-1521
 Project: ManifoldCF
  Issue Type: Bug
  Components: Documentum connector
Affects Versions: ManifoldCF 2.10
Reporter: James Thomas


I find that the time/date constraints in queries to the Documentum server are 
based on the "raw" local time of the ManifoldCF server but appear to take no 
account of the time zones of the two servers.

This can lead to recently modified files not being transferred to the output 
repository when you would naturally expect them to be. I'd like the times to be 
aligned, perhaps by including time zone in the query. In particular, is there a 
way to use UTC perhaps?

Here's an example ...
 * create a folder in Documentum
 * set up a job to point at the folder and output to the file system
 * put two documents into a folder in Documentum
 * Select them, right click and export as CSV (to show the timestamps):

{noformat}
1.png,48489.0,Portable Network Graphics,8/7/2018 9:04 AM,
2.png,28620.0,Portable Network Graphics,8/7/2018 9:04 AM,,{noformat}
Check the local time on the ManifoldCF server machine. Observe that it's 
reporting consistent time with the DM server:
{noformat}
[james@manifold]$ date
Tue Aug  7 09:07:25 BST 2018{noformat}
Start the job and look for the query to Documentum in the manifoldcf.log file 
(line break added for readability):
{noformat}
DEBUG 2018-08-07T08:07:47.297Z (Startup thread) - DCTM: About to execute query= 
(select for READ distinct i_chronicle_id from dm_document where r_modify_date 
>= date('01/01/1970 00:00:00','mm/dd/ hh:mi:ss') and

r_modify_date<=date('08/07/2018 08:07:34','mm/dd/ hh:mi:ss') 

AND (i_is_deleted=TRUE Or (i_is_deleted=FALSE AND a_full_text=TRUE AND 
r_content_size>0)) AND ( Folder('/Administrator/james', DESCEND) ))
^C{noformat}
Notice that the latest date asked for is *before* the modification date of the 
files added to DM. (And is an hour out, see footnote.)
  
 See whether anything has been output by the File System connector. It hasn't:
{noformat}
[james@manifold]$ ls /bigdisc/source/PDFs/timezones/
[james@manifold]$
{noformat}
Now:
 * change the timezone on the ManifoldCF server machine
 * restart the ManifoldCF server and the Documentum processes
 * reseed the job

Check the local time on the ManifoldCF server machine; it has changed:
{noformat}
[james@manifold]$ date
Tue Aug  7 10:10:29 CEST 2018{noformat}
Start the job again and notice that the query has changed by an hour, plus the 
few minutes it took to change the date etc (and is still an hour out, see 
footnote):
{noformat}
r_modify_date<=date('08/07/2018 09:11:02','mm/dd/ hh:mi:ss') 
{noformat}
Observe that the range of dates now covers the timestamps on the DM data, and 
also that some data has now been transferred by the File System connector:
{noformat}
[james@manifold]$ ls 
/bigdisc/source/PDFs/timezones/http/mfserver\:8080/da/component/
drl?versionLabel=CURRENT&objectId=09018000e515
drl?versionLabel=CURRENT&objectId=09018000e516
{noformat}
 

 

[Footnote] It appears that something is trying to take account of Daylight 
Saving Time too.

If I set the server date to a time outside of DST, the query is aligned with 
the current time:

 
{noformat}
[i2e@i2ehost manifold]$ date
 Mon Oct 29 00:01:13 CET 2018

r_modify_date<=date('10/29/2018 00:01:39','mm/dd/ hh:mi:ss') 
{noformat}
But if I set the time inside DST, the time is an hour before:

 
{noformat}
[i2e@i2ehost manifold]$ date
 Sat Oct 27 00:00:06 CEST 2018
r_modify_date<=date('10/26/2018 23:00:26','mm/dd/ hh:mi:ss') 

{noformat}
This is perhaps a Java issue rather than a logic issue in the connector? See 
e.g. [https://stackoverflow.com/questions/6392/java-time-zone-is-messed-up]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Karl Wright (JIRA)]

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

Karl Wright commented on CONNECTORS-1492:
-

[~piergiorgioluc...@gmail.com], I suspect that we (the ManifoldCF PMC) cannot 
distribute Docker images that contain open-source software whose license is 
incompatible with the Apache License.  That would include Postgresql and JCIFS 
connectors, for what it's worth, and we therefore might as well not bother.

You could open a LEGAL ticket to verify this, but seems pretty clear to me.

> GSOC: Add support for Docker
> 
>
> Key: CONNECTORS-1492
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1492
> Project: ManifoldCF
>  Issue Type: New Feature
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: devops, docker, gsoc2018
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to adopt Docker to provide ready to use images with 
> preconfigured architecture stack for ManifoldCF. This will include ManifoldCF 
> itself but also the related database that can be MySQL, PostgreSQL and so on.
> This will help developers to work and put in production a complete ManifoldCF 
> installation.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write Docker files
>  * Write Docker Compose files
>  * Implement unit tests
>  * Build all the integration tests
>  * Write the documentation for new component
> We have a complete documentation about ManifioldCF:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/concepts.html]
> Take a look at our book to understand better the framework and how to extend 
> it in different ways:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Olivier Tavard (JIRA)]

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

Olivier Tavard commented on CONNECTORS-1492:


Hello,

Is this task on the roadmap of MCF yet ? I mean do you have a release date 
already planned for that ?

Anyway if I can help you on this, please tell me.

Thanks,

Best regards,

Olivier

> GSOC: Add support for Docker
> 
>
> Key: CONNECTORS-1492
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1492
> Project: ManifoldCF
>  Issue Type: New Feature
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Major
>  Labels: devops, docker, gsoc2018
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to adopt Docker to provide ready to use images with 
> preconfigured architecture stack for ManifoldCF. This will include ManifoldCF 
> itself but also the related database that can be MySQL, PostgreSQL and so on.
> This will help developers to work and put in production a complete ManifoldCF 
> installation.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write Docker files
>  * Write Docker Compose files
>  * Implement unit tests
>  * Build all the integration tests
>  * Write the documentation for new component
> We have a complete documentation about ManifioldCF:
> [https://manifoldcf.apache.org/release/release-2.9.1/en_US/concepts.html]
> Take a look at our book to understand better the framework and how to extend 
> it in different ways:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)