[
https://issues.apache.org/jira/browse/OAK-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313932#comment-15313932
]
Alex Parvulescu edited comment on OAK-4260 at 6/3/16 10:24 AM:
---------------------------------------------------------------
another point. I just saw a warning related to very long names, this also
probably comes from mongo upgrades but seeing as we're moving from segmentmk ->
segment-tar, the name length should not be an issue, so I think the
{{NameFilteringNodeState}} should not drop anything.
For reference the longest one I saw was 174 chrs.
{code}
*WARN* org.apache.jackrabbit.oak.upgrade.nodestate.NameFilteringNodeState -
Node name 'node-name' too long.
{code}
[edit] created OAK-4426 for this problem
was (Author: alex.parvulescu):
another point. I just saw a warning related to very long names, this also
probably comes from mongo upgrades but seeing as we're moving from segmentmk ->
segment-tar, the name length should not be an issue, so I think the
{{NameFilteringNodeState}} should not drop anything.
For reference the longest one I saw was 174 chrs.
{code}
*WARN* org.apache.jackrabbit.oak.upgrade.nodestate.NameFilteringNodeState -
Node name 'node-name' too long.
{code}
> Define and implement migration from oak-segment to oak-segment-tar
> ------------------------------------------------------------------
>
> Key: OAK-4260
> URL: https://issues.apache.org/jira/browse/OAK-4260
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar, segmentmk, upgrade
> Reporter: Michael Dürig
> Assignee: Tomek Rękawek
> Labels: migration
> Fix For: 1.6
>
>
> We need to come up with a plan, implementation and documentation for how we
> deal with migrating from {{oak-segment}} to {{oak-segment-next}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
