dimension and levels?
>
> Thanks for taggin me along with this.
>
> Roger CamargoUMSS "University"Cochabamba - Bolivia
>
>
> > Date: Mon, 14 Jan 2008 09:56:36 -0500> From: [EMAIL PROTECTED]> To:
> java-user@lucene.apache.org> Subject: Re: How to model hierarchy info to
4 Jan 2008 09:56:36 -0500> From: [EMAIL PROTECTED]> To:
> java-user@lucene.apache.org> Subject: Re: How to model hierarchy info to be
> searched related to a document> > I am not sure why you are afraid of adding
> more fields to the document.> Having 20-30 f
I'm afraid that I would end up not using them for the search, they would
> have each one a field, and because the user can create any number of these
> custom properties they would be hard to query them. Or is there any correct
> way to add them to the document model?
>
> Roge
Thanks for answering.
It seems that there isn't any other way around, having every combination of
dimension and level.
The example for the observations of the dimension, would be as follow, maybe
isn't such an important information to be stored, but type it is.
Dimension name: RegionDimensi
Roger,
Why can;t you have one document for every combination of dimension, level
? Add cube name , id and description too as a field to all documents , all
it would be reduntant information, but you can live with it i suppose?
I think you are developing an application to search a cube ?
what do
I'm trying to index information related to Olap Cubes.
Each cube I'm trying to model it like a document.
The cube have the following information:
ID - Unique identifier for the cube
Name - Name of the cube
Description - Description of the cube
(There can be many dimensions per cube)
Dimensi
