Bug 803519 - alternative to shared file system in JCR
Summary: alternative to shared file system in JCR
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 6.0.0
Assignee: Default User
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-14 21:47 UTC by Gary Hu
Modified: 2018-11-26 17:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-16 09:09:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gary Hu 2012-03-14 21:47:53 UTC
It seems that we could have an alternative to shared file system in JCR based on the exo-jcr document:
  http://docs.jboss.org/exojcr/1.14.3-GA/developer/en-US/html/ch-query-handler-config.html#d0e3549

Have we fully tested? If no, can we test this feature? 

We also need to document it in our reference guide and/or migration guide.

This request comes from GE - https://na7.salesforce.com/500A0000009ewlw

Comment 1 Thomas Heute 2012-06-06 11:47:16 UTC
This is only for Lucene indexes and need to be QAed properly

Comment 2 Jared MORGAN 2012-10-11 01:54:04 UTC
Unassigning from Mark, as he's no longer looking after EPP.

Comment 4 Thomas Heute 2013-04-16 09:09:18 UTC
Default in JPP 6.0 is local storage of lucene indexes. Shared file system is no longer a must have requirement (Can still be preferred in certain scenarios)


Note You need to log in before you can comment on or make changes to this bug.