[
https://issues.apache.org/jira/browse/JENA-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448875#comment-15448875
]
ASF subversion and git services commented on JENA-1228:
-------------------------------------------------------
Commit afdcb37d06ec5b38c06e6f479254fcfbf4821ae7 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=afdcb37 ]
JENA-1228: This closes #165.
> Allow application code to replace part of the standard "Optimize" sequence.
> ---------------------------------------------------------------------------
>
> Key: JENA-1228
> URL: https://issues.apache.org/jira/browse/JENA-1228
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Priority: Minor
>
> A different optimization step can be installed with a global change:
> {noformat}
> Optimize.setFactory((cxt)->new MyNewOptimize(cxt)) ;
> {noformat}
> or on a specific {{Context}}:
> {noformat}
> Optimize.RewriterFactory f = (cxt)->new OptimizeTQ(cxt) ;
> context.set(ARQConstants.sysOptimizerFactory, f) ;
> {noformat}
> This is a complete replacement.
> This JIRA is to allow specific steps to be replaced. This would be quite
> useful for development when specific transforms are being fixed or improved.
> One way to do this is to make {{Optimize}} have protected methods for each
> optimization step thereby exposing the standard policy with the possibility
> of different transforms within that policy.
> Thus:
> {noformat}
> class MyNewOptimize extends Optimize
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
