sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SIS-416) Consider adding StoreResource interface
Date Tue, 24 Jul 2018 14:35:00 GMT

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

Martin Desruisseaux commented on SIS-416:
-----------------------------------------

Added {{org.apache.sis.internal.storage.StoreResource}} in internal packages. We wait for
more experience before to revisit whether this interface should be added in public API.

> Consider adding StoreResource interface
> ---------------------------------------
>
>                 Key: SIS-416
>                 URL: https://issues.apache.org/jira/browse/SIS-416
>             Project: Spatial Information Systems
>          Issue Type: Task
>          Components: Storage
>            Reporter: Martin Desruisseaux
>            Priority: Major
>
> The {{org.apache.sis.storage}} package contains a {{Resource}} interface which is the
root of all resources loaded by a data store ({{FeatureSet}}, {{Aggregate}}, _etc._). The
resources do not tell us which data store created them. In some case we need this information,
for example in order to be fetch the parameters used for opening the data store.
> We could add {{getDataStore()}} method in {{Resource}}, but not all resources are produced
by a data store (a resource could be computed by a model for instance). A possible approach
would be to define this method in a {{StoreResource}} sub-interface, to be implemented only
by resources produces by data stores.
> Some open questions are:
> * What should be the behavior if a resource is used after the data store has been closed;
> * Do we really want those resources to keep a reference to their data store?



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

Mime
View raw message