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

ASF subversion and git services commented on JENA-1757:
-------------------------------------------------------

Commit 493b7f7a853d9b4ee6e47b9d275a0956fec3c7d8 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=493b7f7 ]

JENA-1757: Deprecate GraphStatisticsHandler


> Deprecate GraphStatisticsHandler
> --------------------------------
>
>                 Key: JENA-1757
>                 URL: https://issues.apache.org/jira/browse/JENA-1757
>             Project: Apache Jena
>          Issue Type: Task
>          Components: Core
>    Affects Versions: Jena 3.12.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Graph statistics give the number of for "S P O" where S, P or O can be a 
> wildcard.
> This didn't quite work out for query optimization - the needs for 
> optimization are a little more complicated, needing information such as "if S 
> is going to fixed, estimate the number of "S P O" with out yet knowing what S 
> is fixed as, or it might be one of several values.
> The only significant implementation is \{{GraphMemStatisticsHandler}} for the 
> plain memory graphs. It does exploit the mem indexes to get the count, 
> compared to counting a "find" but the improvement appears to be small. 
> Proposal: deprecate {{GraphStatisticsHandler}}, retain the mem code "just in 
> case".
> This will clear the way for either removal or incompatible change in the 
> future.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to