[
https://issues.apache.org/jira/browse/JENA-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181736#comment-15181736
]
ASF GitHub Bot commented on JENA-1147:
--------------------------------------
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/127
JENA-1147 : Introduce FactoryRDF
FactoryRDF is an interface to abstract the creation of nodes, triples and
quads from constituent elements, e.g. to create a URI Node, the operation takes
a string for the URI. This allows different policies to be slotted in. This PR
covers the use of FactoryRDF by ParserProfile. A PR to follow will use a
caching implementation of FactoryRDF as the default mechanism when parsing.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/127.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #127
----
commit a19aa45a1106ae9ece835a9f17a39663f74f4b78
Author: Andy Seaborne <[email protected]>
Date: 2016-03-05T14:28:18Z
Introduce FactoryRDF and use in ParserProfile.
----
> Add a node cache step to RIOT parsing.
> --------------------------------------
>
> Key: JENA-1147
> URL: https://issues.apache.org/jira/browse/JENA-1147
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
> Affects Versions: Jena 3.0.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> A node cache on the parsing pipeline will reduce memory footprint.
> It may be worth doing different caches for subject/predicate/object as they
> have different characteristics.
> Care is needed because sometimes the parser is not creating stored object
> (e.g. TDB loading) so the cache should measurable not add overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
