Sat, Jun 15
Fri, Jun 14
PropertyLabelResolver is actually used in client, this means it has to access db using DBAccessBase, which means that has to be pushed down to all our Database implementations too and used there instead of ILoadBalancer.
I'm wiring up ProrpertyLabelResolver as part of this now
So the recent open change introduces filtering, also includes the TypeIdsLookup interfance and implementations of it in StaticTypeIdsStore and DatabaseTypeIdsStore. It is as well rebased on and adjusted to use DatabaseTermIdsResolver::resolveTermsViaJoin api.
Thu, Jun 13
Moved back to Ready To Go until sub-tasks are done so that this tasks logic can use them
For the unkown types acquiring issue, we thought we would add another interface that DatabaseTypeIdsResolver would implement and DatabasePropertyTermStore would use.
Wed, Jun 12
Moving back to address the remaining parts of using PropertyLabelResolver
@hoo this is ready for review and to base the patch for parent task on it
Resolving this now as there's no other cases are known to be tested. If new cases appear later we create specific tasks for them.
Clean up seems also to work for the above testing.. I can't find the old texts in relevant stores anymore.
I'm testing now including item terms migration with upper bound id, with the setting:
[ 1000 => MIGRATION_NEW, 100000 => MIGRATION_WRITE_BOTH, 'max' => MIGRATION_OLD ]
Tue, Jun 11
Yeap I actually have access to logstash already. I must have confused it somehow into thinking that there's another logstash for analytics or something.