You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2011/08/23 16:57:29 UTC

[jira] [Created] (JCR-3058) BundleDumper to analyze broken bundles

BundleDumper to analyze broken bundles
--------------------------------------

                 Key: JCR-3058
                 URL: https://issues.apache.org/jira/browse/JCR-3058
             Project: Jackrabbit Content Repository
          Issue Type: New Feature
            Reporter: Thomas Mueller
            Assignee: Thomas Mueller
            Priority: Minor


The BundleReader fails if it can't read a bundle. We should have a tool to analyze broken bundles.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (JCR-3058) BundleDumper to analyze broken bundles

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090152#comment-13090152 ] 

Jukka Zitting commented on JCR-3058:
------------------------------------

It would be great if we could refactor things so that no code duplication between BundleReader and BundleDumper is needed.

> BundleDumper to analyze broken bundles
> --------------------------------------
>
>                 Key: JCR-3058
>                 URL: https://issues.apache.org/jira/browse/JCR-3058
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> The BundleReader fails if it can't read a bundle. We should have a tool to analyze broken bundles.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (JCR-3058) BundleDumper to analyze broken bundles

Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Mueller resolved JCR-3058.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0

This tool can also be used for older version of Jackrabbit.

> BundleDumper to analyze broken bundles
> --------------------------------------
>
>                 Key: JCR-3058
>                 URL: https://issues.apache.org/jira/browse/JCR-3058
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> The BundleReader fails if it can't read a bundle. We should have a tool to analyze broken bundles.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (JCR-3058) BundleDumper to analyze broken bundles

Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090174#comment-13090174 ] 

Thomas Mueller commented on JCR-3058:
-------------------------------------

> It would be great if we could refactor things so that no code duplication between BundleReader and BundleDumper is needed.

I agree, that would be great. However I don't see how it's possible.

> BundleDumper to analyze broken bundles
> --------------------------------------
>
>                 Key: JCR-3058
>                 URL: https://issues.apache.org/jira/browse/JCR-3058
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> The BundleReader fails if it can't read a bundle. We should have a tool to analyze broken bundles.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (JCR-3058) BundleDumper to analyze broken bundles

Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090145#comment-13090145 ] 

Thomas Mueller commented on JCR-3058:
-------------------------------------

The tool doesn't try to detect broken properties currently, who and why would you want to detect them?

> I'm looking at a bundle that has >35 properties, how can I know what is going on?

I used it to manually read the data. I already knew the bundle was broken, because loading the bundle failed, so I knew roughly what the problem was (couldn't parse a timestamp because the year was out of range), but I needed to see the actual data.

For what I used the tool (to easily analyze broken bundles), it works well, but I wonder if adding more complexity is really necessary - I don't need more features currently.

But if have a use case then that's different of course.


> BundleDumper to analyze broken bundles
> --------------------------------------
>
>                 Key: JCR-3058
>                 URL: https://issues.apache.org/jira/browse/JCR-3058
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> The BundleReader fails if it can't read a bundle. We should have a tool to analyze broken bundles.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (JCR-3058) BundleDumper to analyze broken bundles

Posted by "Alex Parvulescu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090130#comment-13090130 ] 

Alex Parvulescu commented on JCR-3058:
--------------------------------------

Good idea.
Is it possible to have the analyzer point to the problems? Rather than relying on manual validation of the properties found in the broken bundle?

Maybe a status message after the dump? along the lines of: 
 - bundle check ok 
or
 - bundle check failed: broken properties are (or might be): p1, p2...

For example, I'm looking at a bundle that has >35 properties, how can I know what is going on?

> BundleDumper to analyze broken bundles
> --------------------------------------
>
>                 Key: JCR-3058
>                 URL: https://issues.apache.org/jira/browse/JCR-3058
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> The BundleReader fails if it can't read a bundle. We should have a tool to analyze broken bundles.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira