Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove JCR properties from root node context #943

Merged
merged 1 commit into from Nov 5, 2015
Merged

remove JCR properties from root node context #943

merged 1 commit into from Nov 5, 2015

Conversation

acoburn
Copy link
Contributor

@acoburn acoburn commented Nov 5, 2015

See: https://jira.duraspace.org/browse/FCREPO-1819

This also removes the descriptors for the Modeshape/Infinispan cluster configuration, which renders the GetCacheManager and GetClusterConfiguration completely unnecessary. So they are removed, too.

@ajs6f
Copy link
Contributor

ajs6f commented Nov 5, 2015

Big time 👍

@acoburn
Copy link
Contributor Author

acoburn commented Nov 5, 2015

@ajs6f a somewhat related question -- there are some lines (currently commented out) related to :

FIXME: removing due to performance problems, esp. w/ many files on federated filesystem

 b.add(create(subject(), HAS_OBJECT_COUNT.asNode(), createLiteral(String
                 .valueOf(getRepositoryCount(repository)))));
 b.add(create(subject(), HAS_OBJECT_SIZE.asNode(), createLiteral(String
                 .valueOf(getRepositorySize(repository)))));

Should those be removed, too?

@ajs6f
Copy link
Contributor

ajs6f commented Nov 5, 2015

@awoods @escowles @cbeer What do you think? People want that info, but it is damn hard, and I think we decided that with federation, nearly impossible.

@escowles
Copy link
Contributor

escowles commented Nov 5, 2015

+1 to removing the object count/size here. This would be a great thing to include in webapp-plus, so people who weren't using federation could add it in.

@ajs6f
Copy link
Contributor

ajs6f commented Nov 5, 2015

@escowles Are you talking about actually modularizing "all-repo" stats so that people could plug in what they want?

@escowles
Copy link
Contributor

escowles commented Nov 5, 2015

I was thinking we could literally plug in those two lines of code as an optional module. They work fine if you aren't using federation. Of course,people could plug in alternate implementations if they wanted to.

Of course, we could do this in fcrepo4: if there is an appropriate bean injected, then add those properties, otherwise just skip them.

// Get the cluster configuration, if available
// this ugly test checks to see whether this is an ordinary JCR
// repository or a ModeShape repo, which will possess the extra info
if (JcrRepository.class.isAssignableFrom(repository.getClass())) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this cluster information is still valuable... especially with the recent flurry of interest in clustering.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The info may be valuable, bu that does not mean it should be published here. Perhaps in logging statements.

@ajs6f
Copy link
Contributor

ajs6f commented Nov 5, 2015

@escowles I would prefer an entirely separate module. I wouldn't mind shoving the Metrics-produced stats in there too.

@awoods
Copy link

awoods commented Nov 5, 2015

Normally I do not like dead code, but in this case, it continues to serve as a good reminder. I would suggest leaving this commented-out block around until we actually split the logic into a new, separate module.

@acoburn
Copy link
Contributor Author

acoburn commented Nov 5, 2015

@awoods ok, then I will leave this PR as it currently stands; it is ready for review.

@escowles
Copy link
Contributor

escowles commented Nov 5, 2015

@awoods: I've created a ticket for an external module for repository object/byte counts: https://jira.duraspace.org/browse/FCREPO-1820

@ajs6f
Copy link
Contributor

ajs6f commented Nov 5, 2015

I think this is ready to go. Any objections?

awoods pushed a commit that referenced this pull request Nov 5, 2015
remove JCR properties from root node context
@awoods awoods merged commit 021a8f8 into fcrepo:master Nov 5, 2015
@acoburn acoburn deleted the fcrepo-1819 branch November 6, 2015 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants