Bug 803519

Summary:	alternative to shared file system in JCR
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	Gary Hu <ghu>
Component:	Portal	Assignee:	Default User <jbpapp-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	epp-bugs, hfnukal, theute
Target Milestone:	---
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-16 09:09:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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)