Alfresco discussion and collaboration. Stick around a few hours after asking a question.
Official support for Enterprise subscribers: support.alfresco.com.
Join in the conversation by getting an IRC client and connecting to #alfresco at Freenode. Our you can use the IRC web chat.
More information about the channel is in the wiki.
More help is available in this list of resources.
2019-10-23 07:25:59 GMT <alfresco-discord> <dgradecak> good morning good people, does anyone know what for "activemq" is all used, except for renditions? Is there anything else?
2019-10-23 07:42:31 GMT <AFaust> Well - other than renditions, only the async event handling (which the new renditions already use as a basis)
2019-10-23 07:52:11 GMT <angelborroy> ~HtmlLogger flushlog
2019-10-23 07:52:11 GMT <alfbot> angelborroy: Woooosh, your log has been flushed...
2019-10-23 08:39:38 GMT <alfresco-discord> <dgradecak> did you try to send the async events to amq on community?
2019-10-23 14:26:18 GMT <alfresco-discord> <dgradecak> @angel.borroy: do you know why https://github.com/Alfresco/alfresco-sync-events is depreacted?
2019-10-23 14:26:19 GMT <alfbot> Title:GitHub - Alfresco/alfresco-sync-events: Alfresco Sync Events (Deprecated) (at github.com)
2019-10-23 14:26:24 GMT <alfresco-discord> <dgradecak> or anyone else of course
2019-10-23 15:57:03 GMT <hi-ko> @dgradecak I don't know but I guess the deprecation of sync is as usual: functionality was to limited / customer complained but new Alfresco owner does not spend money in refactoring if it's not essential like transformation, search
2019-10-23 16:02:49 GMT <hi-ko> ~later tell angelborroy @dgradecak is aking for amq usage except for renditions. What are the plans for solr tracker replacements?
2019-10-23 16:02:49 GMT <alfbot> hi-ko: The operation succeeded.
2019-10-23 16:05:06 GMT <alfbot> angelborroy: Sent 2 minutes ago: <hi-ko> @dgradecak is aking for amq usage except for renditions. What are the plans for solr tracker replacements?
2019-10-23 16:06:01 GMT <angelborroy> Designing SOLR Tracker as Spring Boot services now
2019-10-23 16:06:21 GMT <angelborroy> And after some time also Query and Admin as Spring Boot services
2019-10-23 16:06:51 GMT <angelborroy> To have something like an standard SOLR 8 (supporting SolrCloud) in the end
2019-10-23 16:07:05 GMT <angelborroy> Obviously these are only plans and the timeline is not closed
2019-10-23 16:22:21 GMT <hi-ko> ~later tell angelborroy: decoupling the tracker from solr makes sense and deployment easier. does this mean that tracker's conceptual architecture will not change from polling to messaging?
2019-10-23 16:37:10 GMT <alfresco-discord> <dgradecak> hi-ko: I built a spring boot solr tracker that I am using for many integrations app, with a filtering of nodes. When I say solr tracker, it is an app that uses the same alfresco/solr/api and keeps track of nodes
2019-10-23 16:38:02 GMT <alfresco-discord> <dgradecak> https://github.com/PleoSoft/peltas-community
2019-10-23 16:38:03 GMT <alfbot> Title:GitHub - PleoSoft/peltas-community: Peltas is a friendly, smart and ready-to-use BI tool for Alfresco Content Services (at github.com)
2019-10-23 16:38:44 GMT <alfresco-discord> <dgradecak> using it to send "filtered nodes" to jms also, but can be used with a license for alfresco audit
2019-10-23 16:39:57 GMT <hi-ko> @dgradecak: thanks. peltas-community is already on our evaluation list ;-)
2019-10-23 16:40:22 GMT <alfresco-discord> <dgradecak> check the dev branch, there is some sample how to use it with any kind of "writers"
2019-10-23 16:41:03 GMT <hi-ko> at the moment we tend more to an aproach similar to Jeffs messaging use case to build up and manage change events
2019-10-23 16:41:31 GMT <alfresco-discord> <dgradecak> well, each transaction is mainly a change
2019-10-23 16:41:40 GMT <alfresco-discord> <dgradecak> and that is what the solr api provides
2019-10-23 16:42:22 GMT <alfresco-discord> <dgradecak> like I told to Jeff, with the "behavior" approach (that is what sync does mainly with apache camel
2019-10-23 16:42:36 GMT <hi-ko> sure - and as long alfresco does not change the cluster concept thay can't change the core behind the tracker api
2019-10-23 16:42:46 GMT <alfresco-discord> <dgradecak> but you lose "old node info", which with solr api (peltas-community) you always can "reindex" the way you want
2019-10-23 16:43:58 GMT <alfresco-discord> <dgradecak> I mena, you need that approach from day one
2019-10-23 16:44:19 GMT <hi-ko> our plan so far is not to use jeffs implementation but the policy design. what we already have from our sync server is a pull all aproach
2019-10-23 16:45:43 GMT <hi-ko> we already used the solr-tracker api for sync clients years ago but we didn't like the transaction based grouping
2019-10-23 16:48:02 GMT <hi-ko> that's the reason why we implemnted our own node based sync for reindex.
2019-10-23 16:49:06 GMT <alfresco-discord> <dgradecak> how do you sync it than? based on what exactly if it is not transactions?
2019-10-23 16:52:28 GMT <alfresco-discord> <dgradecak> regarding my question about sync being deprecated, the project on github is marked as deprecated but no classes in the repository project that uses it are marked as deprecated like org.alfresco.repo.events.EventsServiceImpl, where apache camel is used to send those events to active mq
2019-10-23 16:52:41 GMT <hi-ko> dgradecak: maybe we could combine both for the reindex use case: using this only once to build up our own db schema with a fact table storing the expensinve properties which are not mass queryable and a last change table to avoid reading a node too often
2019-10-23 16:52:43 GMT <alfresco-discord> <dgradecak> so it is a bit obscure
2019-10-23 16:53:03 GMT <alfresco-discord> <dgradecak> that is exactly what peltas does hi-ko
2019-10-23 16:53:29 GMT <alfresco-discord> <dgradecak> but with the solr api
2019-10-23 16:53:57 GMT <hi-ko> so I will take a deeper look ;-)
2019-10-23 16:54:43 GMT <hi-ko> today we sync based on custom db queries
2019-10-23 16:54:57 GMT <hi-ko> creating the list of nodes to sync
2019-10-23 16:55:31 GMT <dgradecak> ping me for a skype call or so, it would be good to get in touch (daniel.gradecak)
2019-10-23 19:24:08 GMT <hi-ko> ~later tell angelborroy will alfresco open source / publish alfresco-document-transformation-engine or is it only provided a compiled amp?
2019-10-23 20:09:25 GMT <alfresco-discord> <dgradecak> this one ? https://github.com/Alfresco/alfresco-transform-core
2019-10-23 20:09:26 GMT <alfbot> Title:GitHub - Alfresco/alfresco-transform-core (at github.com)
2019-10-23 20:11:27 GMT <alfresco-discord> <dgradecak> mainly you can run them as spring boot apps, but the paths are hardcoded, while it could be as easy as having a config property - but it makes things harder for the community 😉
The other logs are at http://esplins.org/hash_alfresco