Here is what I am trying to do in short with a document collection of 2-3 million.
"Index1" has column1 and column2 in the map. There is a change request to add another column to the index but if I change map, its going to rebuild the entire index (Am I even right on this one?).
What I would like to do it create a new index "Index2" with the appropriate columns and when its done, rename it back to "Index1"
*Why would I even want to to this?* I don't want any existing client application to have to change their code base to start querying on the new column.
Another possible use case is If I decide to make one of my fields Analyzed or change an Analyzer on an field.I would still want existing clients to be able to use the old index.
> Here is what I am trying to do in short with a document collection of
> 2-3 million.
> "Index1" has column1 and column2 in the map. There is a change request
> to add another column to the index but if I change map, its going to
> rebuild the entire index (Am I even right on this one?).
> What I would like to do it create a new index "Index2" with the
> appropriate columns and when its done, rename it back to "Index1"
> *Why would I even want to to this?*
> I don't want any existing client application to have to change their
> code base to start querying on the new column.
> Another possible use case is If I decide to make one of my fields
> Analyzed or change an Analyzer on an field.I would still want existing
> clients to be able to use the old index.
Just to clarify the Client is an UI application where I am exposing the fields to query based on the metadata for the UI. Basically, I would change my metadata to start exposing the field for search without recompiling the code. This would work because, I am using the Advanced Lucene query to dynamically build Lucene search/query strings.
On Tuesday, August 14, 2012 5:40:11 PM UTC-7, Juma wrote:
> Hi,
> Is there a way to rename an index?
> Here is what I am trying to do in short with a document collection of 2-3 > million.
> "Index1" has column1 and column2 in the map. There is a change request to > add another column to the index but if I change map, its going to rebuild > the entire index (Am I even right on this one?).
> What I would like to do it create a new index "Index2" with the > appropriate columns and when its done, rename it back to "Index1"
> *Why would I even want to to this?* > I don't want any existing client application to have to change their code > base to start querying on the new column.
> Another possible use case is If I decide to make one of my fields Analyzed > or change an Analyzer on an field.I would still want existing clients to be > able to use the old index.
> Just to clarify the Client is an UI application where I am exposing the
> fields to query based on the metadata for the UI. Basically, I would change
> my metadata to start exposing the field for search without recompiling the
> code. This would work because, I am using the Advanced Lucene query to
> dynamically build Lucene search/query strings.
> On Tuesday, August 14, 2012 5:40:11 PM UTC-7, Juma wrote:
>> Hi,
>> Is there a way to rename an index?
>> Here is what I am trying to do in short with a document collection of 2-3
>> million.
>> "Index1" has column1 and column2 in the map. There is a change request to
>> add another column to the index but if I change map, its going to rebuild
>> the entire index (Am I even right on this one?).
>> What I would like to do it create a new index "Index2" with the
>> appropriate columns and when its done, rename it back to "Index1"
>> *Why would I even want to to this?*
>> I don't want any existing client application to have to change their code
>> base to start querying on the new column.
>> Another possible use case is If I decide to make one of my fields
>> Analyzed or change an Analyzer on an field.I would still want existing
>> clients to be able to use the old index.
Nope, the users wouldn't add new fields to the index.
It would be a power user or a developer changing the index definition directly using Raven Studio (after testing it). They would also change the meta data definition that allows searching by the new field.
Then the next time the end user uses the Search UI, the new field will be available for searching (fully indexed).
On Tuesday, August 14, 2012 6:00:28 PM UTC-7, Kijana Woodard wrote:
> And users are able to add new fields which need to be indexed? > On Aug 14, 2012 7:47 PM, "Juma" <jum...@gmail.com <javascript:>> wrote:
>> Just to clarify the Client is an UI application where I am exposing the >> fields to query based on the metadata for the UI. Basically, I would change >> my metadata to start exposing the field for search without recompiling the >> code. This would work because, I am using the Advanced Lucene query to >> dynamically build Lucene search/query strings.
>> On Tuesday, August 14, 2012 5:40:11 PM UTC-7, Juma wrote:
>>> Hi,
>>> Is there a way to rename an index?
>>> Here is what I am trying to do in short with a document collection of >>> 2-3 million.
>>> "Index1" has column1 and column2 in the map. There is a change request >>> to add another column to the index but if I change map, its going to >>> rebuild the entire index (Am I even right on this one?).
>>> What I would like to do it create a new index "Index2" with the >>> appropriate columns and when its done, rename it back to "Index1"
>>> *Why would I even want to to this?* >>> I don't want any existing client application to have to change their >>> code base to start querying on the new column.
>>> Another possible use case is If I decide to make one of my fields >>> Analyzed or change an Analyzer on an field.I would still want existing >>> clients to be able to use the old index.
On Wed, Aug 15, 2012 at 3:40 AM, Juma <juma...@gmail.com> wrote:
> Hi,
> Is there a way to rename an index?
> Here is what I am trying to do in short with a document collection of 2-3
> million.
> "Index1" has column1 and column2 in the map. There is a change request to
> add another column to the index but if I change map, its going to rebuild
> the entire index (Am I even right on this one?).
> What I would like to do it create a new index "Index2" with the
> appropriate columns and when its done, rename it back to "Index1"
> *Why would I even want to to this?*
> I don't want any existing client application to have to change their code
> base to start querying on the new column.
> Another possible use case is If I decide to make one of my fields Analyzed
> or change an Analyzer on an field.I would still want existing clients to be
> able to use the old index.
Just a quick clarification question (probably newbie):
Since the client code has to explicitly use the index name, I would think as long as there is no structural change in the index, this would be a non-issue right? Is there a underlying technical challenge involved?
On Tuesday, August 14, 2012 11:59:50 PM UTC-7, Oren Eini wrote:
> Juma, > We have no facility for renaming indexes.
> On Wed, Aug 15, 2012 at 3:40 AM, Juma <jum...@gmail.com <javascript:>>wrote:
>> Hi,
>> Is there a way to rename an index?
>> Here is what I am trying to do in short with a document collection of 2-3 >> million.
>> "Index1" has column1 and column2 in the map. There is a change request to >> add another column to the index but if I change map, its going to rebuild >> the entire index (Am I even right on this one?).
>> What I would like to do it create a new index "Index2" with the >> appropriate columns and when its done, rename it back to "Index1"
>> *Why would I even want to to this?* >> I don't want any existing client application to have to change their code >> base to start querying on the new column.
>> Another possible use case is If I decide to make one of my fields >> Analyzed or change an Analyzer on an field.I would still want existing >> clients to be able to use the old index.
Juma,
Indexes are fairly involved internally.
Renaming them isn't as simple as just changing the name, it would means
moving directories (while indexing is still running), updating lot of
internal values, etc.
On Wed, Aug 15, 2012 at 5:57 PM, Juma <juma...@gmail.com> wrote:
> Thanks Oren.
> Just a quick clarification question (probably newbie):
> Since the client code has to explicitly use the index name, I would think
> as long as there is no structural change in the index, this would be a
> non-issue right? Is there a underlying technical challenge involved?
> Thanks,
> Juma
> On Tuesday, August 14, 2012 11:59:50 PM UTC-7, Oren Eini wrote:
>> Juma,
>> We have no facility for renaming indexes.
>> On Wed, Aug 15, 2012 at 3:40 AM, Juma <jum...@gmail.com> wrote:
>>> Hi,
>>> Is there a way to rename an index?
>>> Here is what I am trying to do in short with a document collection of
>>> 2-3 million.
>>> "Index1" has column1 and column2 in the map. There is a change request
>>> to add another column to the index but if I change map, its going to
>>> rebuild the entire index (Am I even right on this one?).
>>> What I would like to do it create a new index "Index2" with the
>>> appropriate columns and when its done, rename it back to "Index1"
>>> *Why would I even want to to this?*
>>> I don't want any existing client application to have to change their
>>> code base to start querying on the new column.
>>> Another possible use case is If I decide to make one of my fields
>>> Analyzed or change an Analyzer on an field.I would still want existing
>>> clients to be able to use the old index.
On Wednesday, August 15, 2012 8:46:33 AM UTC-7, Oren Eini wrote:
> Juma, > Indexes are fairly involved internally. > Renaming them isn't as simple as just changing the name, it would means > moving directories (while indexing is still running), updating lot of > internal values, etc.
> On Wed, Aug 15, 2012 at 5:57 PM, Juma <jum...@gmail.com <javascript:>>wrote:
>> Thanks Oren.
>> Just a quick clarification question (probably newbie):
>> Since the client code has to explicitly use the index name, I would think >> as long as there is no structural change in the index, this would be a >> non-issue right? Is there a underlying technical challenge involved?
>> Thanks, >> Juma
>> On Tuesday, August 14, 2012 11:59:50 PM UTC-7, Oren Eini wrote:
>>> Juma, >>> We have no facility for renaming indexes.
>>> On Wed, Aug 15, 2012 at 3:40 AM, Juma <jum...@gmail.com> wrote:
>>>> Hi,
>>>> Is there a way to rename an index?
>>>> Here is what I am trying to do in short with a document collection of >>>> 2-3 million.
>>>> "Index1" has column1 and column2 in the map. There is a change request >>>> to add another column to the index but if I change map, its going to >>>> rebuild the entire index (Am I even right on this one?).
>>>> What I would like to do it create a new index "Index2" with the >>>> appropriate columns and when its done, rename it back to "Index1"
>>>> *Why would I even want to to this?* >>>> I don't want any existing client application to have to change their >>>> code base to start querying on the new column.
>>>> Another possible use case is If I decide to make one of my fields >>>> Analyzed or change an Analyzer on an field.I would still want existing >>>> clients to be able to use the old index.
