[
https://issues.apache.org/jira/browse/OAK-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510430#comment-13510430
]
Michael Dürig commented on OAK-493:
-----------------------------------
I agree this seems to be more trouble than it's worth.
We should employ a more general mechanism to prevent storing a lot of duplicate
string values if this turns out to be a problem. But I think this is better
tackled at a lower level.
> Drop fallback in Node#getPrimaryType
> ------------------------------------
>
> Key: OAK-493
> URL: https://issues.apache.org/jira/browse/OAK-493
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: angela
>
> currently the implementation of NodeImpl#getPrimaryType has a fallback if the
> primary type
> property is missing (to nt:unstructured). while that might have been useful
> in the beginning
> when be basically didn't have anything running, i am not convinced that this
> is really
> a reasonable setup for a mature implementation...
> the regression i was referring to in OAK-490 wasn't caused by the move itself
> but by
> the fact that i didn't (nor intend to) copy over that shortcut to the node
> type manager.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
