Thilo Goetz wrote:
Marshall Schor wrote:
Adam Lally wrote:
On 12/22/06, Marshall Schor [EMAIL PROTECTED] wrote:
If we had filtering predicates as part of an index specification,
then we
could create indexes over subsets of types quite arbitrarily. Could
this
more general mechanism serve
Marshall Schor wrote:
Re: Need for Global indexes
snip
What is the use case or the global view set of indexes? I can't recall
the use-case for this, beyond
being able to get all the data. This thread has suggested other
utilities that can effectively
merge the results from other view's
A collection of quotes from Thilo about global indexes. After reading
all these I think I finally might be on the same wavelength... (we'll
see in a moment :)
On 12/22/06, Thilo Goetz [EMAIL PROTECTED] wrote:
snip/
Global indexes should be shared. That is
also the spirit of the OASIS draft,
* There is one Global Index Repository in the CAS (accessible by
CAS.getGlobalIndexRepository() and CAS.addFsToGlobalIndexes())
* Each view has its own Index Repository, containing only the indexes
that are specific to that view. (accessible by
CasView.getIndexRepository() and
Adam Lally wrote:
On 12/22/06, Marshall Schor [EMAIL PROTECTED] wrote:
If we had filtering predicates as part of an index specification,
then we
could create indexes over subsets of types quite arbitrarily. Could this
more general mechanism serve this purpose better than views?
I'm not sure
Marshall Schor wrote:
Adam Lally wrote:
On 12/22/06, Marshall Schor [EMAIL PROTECTED] wrote:
If we had filtering predicates as part of an index specification,
then we
could create indexes over subsets of types quite arbitrarily. Could this
more general mechanism serve this purpose better than
I haven't thought this through yet, but here's how I see indexes and
their relation to views right now. Let me know if this agrees with your
views, or how it differs.
The index repository is a set of indexes, at least right now. All it
can do is to give you indexes. The index repository of
On 12/21/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I haven't thought this through yet, but here's how I see indexes and
their relation to views right now. Let me know if this agrees with your
views, or how it differs.
The index repository is a set of indexes, at least right now. All it
can do
Adam Lally wrote:
Thilo's stuff snipped
I think this basically makes sense. I want to clarify though, that
what we *do* currently have different indexes for each view (for
example each view has its own annotation index, which holds the
annotations relating to that view's sofa). This is done by
Adam Lally wrote:
On 12/21/06, Thilo Goetz [EMAIL PROTECTED] wrote:
I didn't mean to suggest to have duplicate indexes. What I meant to say
was, each view should have its own annotation index. In the CAS, each
of these annotation indexes can be accessed separately. In fact, I
think this is
Re: Need for Global indexes
Adam Lally wrote:
snip
Moreover, I think the reverse direction should be true -- indexing an
FS in a view's index repository DOES add it (at least conceptually) to
indexes that apply to the CAS as a whole. I liked this latter idea
because it provided a way to
If we think of a CasView as a way of accessing a subset of the data
in the CAS, what are the pluses and minuses of having every view
have the same (shared) index definitions? Would it make more sense
to have each view have its own non-shared set of indexes / definitions?
Pluses:
- A view which
12 matches
Mail list logo
