[
https://issues.apache.org/jira/browse/OAK-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022719#comment-16022719
]
Vikas Saurabh commented on OAK-5970:
------------------------------------
[~chetanm], I'd prefer
bq. ApproximateCounter based - Uses approx counter support to do the estimation
There are 2 arguments that I can think of:
* ETA is implicitly "estimated" TA
* Iiuc, mongo query would still be deep query (ie depth in \{5, 6, 7, ... \}) -
that would be bad for perf ... for count mongo would still do an index scan \[0]
\[0]:
{noformat}
> db.nodes.explain().count({_id:{$regex:"^3:/content/dam"}})
{
"queryPlanner" : {
"plannerVersion" : 1,
"namespace" : "aem-author.nodes",
"indexFilterSet" : false,
"parsedQuery" : {
"_id" : /^3:\/content\/dam/
},
"winningPlan" : {
"stage" : "COUNT",
"inputStage" : {
"stage" : "FETCH",
"inputStage" : {
"stage" : "IXSCAN",
"keyPattern" : {
"_id" : 1
},
"indexName" : "_id_",
"isMultiKey" : false,
"isUnique" : true,
"isSparse" : false,
"isPartial" : false,
"indexVersion" : 1,
"direction" : "forward",
"indexBounds" : {
"_id" : [
"[\"3:/content/dam\",
\"3:/content/dan\")",
"[/^3:/content/dam/,
/^3:/content/dam/]"
]
}
}
}
},
"rejectedPlans" : [ ]
},
"serverInfo" : {
"host" : "durden",
"port" : 27017,
"version" : "3.2.11",
"gitVersion" : "009580ad490190ba33d1c6253ebd8d91808923e4"
},
"ok" : 1
}
{noformat}
> (Re-)Indexing: estimate progress / ETA
> --------------------------------------
>
> Key: OAK-5970
> URL: https://issues.apache.org/jira/browse/OAK-5970
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing
> Reporter: Thomas Mueller
> Assignee: Chetan Mehrotra
> Fix For: 1.8
>
>
> Reindexing can take a long time, so it would be good if we can estimate where
> we are at (for example in percent of the relevant number of nodes). It might
> also be possible to estimate when indexing will be done, and the current path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
