This repository has been archived by the owner on Nov 28, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
[Importer] Consistent API to map element IDs in meta-values #56
Milestone
Comments
dnaber-de
added a commit
that referenced
this issue
Feb 14, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 14, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 14, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 14, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 14, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 14, 2016
Apply the filter to each record if it is a multi-record meta #56
dnaber-de
added a commit
that referenced
this issue
Feb 14, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 15, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 15, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 17, 2016
Uses by meta filter API to address clearly an object related meta record #56
dnaber-de
added a commit
that referenced
this issue
Feb 17, 2016
Use Type\MetaIndexRecord types to address unfilterable meta records. Those will be stored in object storages to be quickly iteratable #56
dnaber-de
added a commit
that referenced
this issue
Feb 17, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 17, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 17, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 17, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 17, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 18, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 18, 2016
dnaber-de
added a commit
that referenced
this issue
Feb 18, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Whenever element IDs are stored as meta data value, the relation will break on import when these IDs changes. So right before we import meta data we provide a filter passing the meta data and the instance of the ID mapper.
As everything else, this API has to be independent of the progress of the import, so it is not stated that the ID is available at the moment of the first processing.
This will be part of the meta-data importer described in #57
Todo:
Import\Filter\ValueFilterableInterface
.SingleIdMetaValueFilter
,RecursiveIdMetaValueFilter
Import\Data\MetaFilterListInterface
andImport\Data\MetaFilterListInterface
Import\Service\ImportMetaFilterInterface
andImport\Service\ImportMetaFilter
w2m_import_meta_not_filterable
(in the connector service) when a filter is not filterable right nowImport\Data\ImportListeningMetaFilterList
Import\Module\ResolvingPendingMetaFilter
Controller\MetaFilterApi
w2m_import_meta_filter
Data\MetaFilterList
to have only one filter instance per type/key pair. If one of the composed filter is not able to filter the value, no other filter must be applied in the first time (Service\ImportMetaFilter
). Otherwise we would get in trouble with multiple record metas on clean-up.The text was updated successfully, but these errors were encountered: