Greg,
Prior to the 3.0 release, there were some discussions about pushing the
Resource Index out of the core and repackaging it as a service. Similar
to GSearch, the Resource Index would use Fedora's messaging service to
subscribe to repository events to trigger updates.
We didn't get to it mostly for lack of time, but it's still on the table
for a future release. There's an open issue for this in JIRA (sorry,
don't have the link handy).
-Eddie
On 10/30/2008 01:48 AM, Greg Jansen is rumored to have said:
> Hey, we've got Mulgara running in remote mode as described below, using
> Mulgara's default #server1 servername. The fedora-rebuild scripts
> require Mulgara to be running, but not Fedora. So what I did was create
> two /etc/init.d scripts, one to start both and one to just start Mulgara
> alone.
>
> I do think the architecture could be further decoupled by allowing
> fedora to run while also reindexing the resource index. However, you've
> got to block or track all object changes while that the index process
> completes, something that seems more likely in the next release, which
> promises JTA support. Edwin, do fedora developers have any plans or
> thoughts about that?
>
> thanks,
> Greg Jansen
> Carolina Digital Repository
> UNC Chapel Hill
>
> Edwin Shin wrote:
>> (moving to fedora users)
>>
>> On 10/29/2008 11:15 PM, Benjamin O'Steen is rumored to have said:
>> <snip/>
>>
>>
>>> Some documentation on the limits/breadth of support would be most
>>> appreciated, as the statement 'SPARQL support' might pose problems for
>>> managing user expectations.
>>
>> I'm not positive what the latest state of SPARQL support in Mulgara
>> is--it's either complete or just about. Mid-summer (before Mulgara
>> 2.0.0), about 95% of SELECT queries were supported, where the main
>> thing missing was ordering by expression instead of by a variable.
>> Also at that time, ASK, DESCRIBE and CONSTRUCT were not supported, but
>> these are now supported (or at least I see the code for it now).
>>
>>
>>> (So far, I have got the in-vm mulgara to understand a SELECT query, but
>>> it fails to reply with any results. A person with only SPARQL experience
>>> might be similarly stuck.)
>>>
>>
>> You'll still need to include a FROM clause in your SPARQL query if
>> that helps (e.g. "select * from <#ri> where { ?s ?p ?o }")--there's no
>> default model set, which come to think of it, we should consider doing.
>>
>>
>>> On a similar note, I was also interested in having an external Mulgara
>>> store coupled to Fedora. If anyone has a walkthrough on how to set this
>>> up, I'd love to read it. I have set the host param in the fedora.fcfg,
>>> and have Mulgara's web UI happily running on /risearch. However, I
>>> haven't been able to guess the process for creating the graph for Fedora
>>> to use, mainly due to my inexperience with native mulgara, so rebuilding
>>> fails, and Mulgara seems empty.
>>>
>>
>> In datastore configuration for Mulgara in fedora.fcfg, set "remote" to
>> "true", and set the "host" (and "port" if you're not using the default
>> 1099) parameter to the host Mulgara is running on (e.g. "localhost").
>> You also need to ensure that the serverName parameter matches your
>> remote instance of Mulgara (e.g. start mulgara with "-s fedora" or
>> change serverName in fedora.fcfg to "server1", which is Mulgara's
>> default). I think that's it ;) Let me know if that works for you. Then
>> this should go up on the wiki.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
