Daily Log for #alfresco IRC Channel

Alfresco discussion and collaboration. Stick around a few hours after asking a question.

Official support for Enterprise subscribers: support.alfresco.com.

Joining the Channel:

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.

Getting Help

More help is available in this list of resources.

Daily Log for #alfresco

2020-01-17 10:31:48 GMT <AFaust> I don't know why it took me so long before tracing the @author tag in Alfresco's Smart Folder code to the person behind it, but now I finally understand why this whole code / implementation feels so out of place and un-Alfresco, why it is extremely unextensible / unfixable without source patches, and why it is essentially dormant/stale.

2020-01-17 10:32:45 GMT <AFaust> But that is what you get when you (as a software vendor) outsource your engineering work to near-/off-shoring companies without an apparent familiarity of your core code DNA...

2020-01-17 10:56:39 GMT <AFaust> angelborroy: qq, who's left at the Search team now (apart from yourself)?

2020-01-17 10:57:52 GMT <angelborroy> Alex Mukha, Tom Page and Sease guys

2020-01-17 10:58:10 GMT <angelborroy> https://sease.io

2020-01-17 10:58:11 GMT <alfbot> Title:Home - Sease (at sease.io)

2020-01-17 11:03:00 GMT <AFaust> At least I know those two Alfresco names - I was afraid they'd be some (relatively fresh) unknowns

2020-01-17 11:03:41 GMT <angelborroy> Those Sease guys are also great

2020-01-17 11:03:46 GMT <angelborroy> Very confident now with the team

2020-01-17 11:06:45 GMT <angelborroy> btw, I guess next release will include some interesting performance improvements based in what we talked some days ago

2020-01-17 11:07:32 GMT <angelborroy> That could be the first “real” feature to be considered to upgrade Search Services

2020-01-17 11:07:59 GMT <angelborroy> We are also working on Content Store removal, that will be nice in terms of performance and maintainabilty

2020-01-17 11:08:11 GMT <angelborroy> But this will be available later (I guess)

2020-01-17 11:17:36 GMT <AFaust> You mean that "massive amounts of gz-compressed merged JSON + text/plain files" content store?

2020-01-17 11:18:06 GMT <angelborroy> Right

2020-01-17 11:18:17 GMT <angelborroy> That could be a better name :D

2020-01-17 11:18:32 GMT <AFaust> Without re-introducing the need to hit DBs again on cascading updates? Ok, colour me intrigued...

2020-01-17 11:19:06 GMT <angelborroy> We are also planning to remove that CascadeTracker

2020-01-17 11:19:18 GMT <angelborroy> But that task is still not taken

2020-01-17 11:20:42 GMT <AFaust> Any idea on how many of these changes would be backwards-compatible with older Repository versions, e.g. work in a ASS 1.5 + ACS 6.0 scenario (maybe) -- not talking about "officially supported" here, only technically possible...

2020-01-17 11:21:15 GMT <AFaust> Or maybe this going to be ASS 2.x?

2020-01-17 11:21:28 GMT <angelborroy> Yep, that removal will be part of 2.x

2020-01-17 11:22:14 GMT <angelborroy> I guess that could work with 6.0+

2020-01-17 11:22:17 GMT <angelborroy> But I’m not sure

2020-01-17 17:51:53 GMT <FileSysOrg> RE: fileServersNG - there is code in the JFileServer core that works with either Hazelcast 2.x or Hazelcast 3.x, the appropriate version is loaded dynamically at startup by probing to see what classes are available, in the fileServersNG pom.xml it's set to use the provided Hazelcast library

End of Daily Log

The other logs are at http://esplins.org/hash_alfresco