[
https://issues.apache.org/jira/browse/OAK-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025869#comment-14025869
]
Tommaso Teofili commented on OAK-1878:
--------------------------------------
bq. It is actually possible to update the fix version field of a closed issue
this is project specific, as far as I can remember this depends on Jira project
setup (e.g. LUCENE-1499 is closed with a fix version which is not editable).
Generally having fix versions for different versions in the same issue is ok
for the sake of simplicity, even if the fixed happened in two very different
times; however it may be a bit confusing to have the same issue appearing in
different release notes of different versions. For this specific case I think
it makes sense to follow your advice, I'll mark it as duplicate of OAK-1800 and
update the fix version there.
> Backport OAK-1800 (configurable no. of rows) to branch 1.0
> ----------------------------------------------------------
>
> Key: OAK-1878
> URL: https://issues.apache.org/jira/browse/OAK-1878
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-solr
> Affects Versions: 1.0
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 1.0.1
>
>
> It'd be good to backport the fix for OAK-1800 to branch 1.0 in order to have
> the no. of rows to be configurable (simplifying setup and improving
> performances).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
