nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Indexing engine in D7

metzorg

Hi,

Do you know what is the Indexing engine in Documentum versio 7?

Is it Apache Lucene or something else?

Is it possible to migrate current FAST indexes with Lucene?

Thanx,

Find more posts tagged with

Comments

njain

Here is what Jamal Shakra, Product Manager, Documentum Platform Products has to say.

"We will support FAST and our own which is based on combination of Lucene and xml technology we acquired."

metzorg

You still support the technology which MS bought... omg lol.

njain

Was curious to know more about remark. Can you let us know more of the context of your post? We appreciate all comments, critical or not and always want to know more. Thanks.

metzorg

Well I have my thoughts about the MS technology....and there has been a lot of bugs with FAST. Even the old Verity worked better.

I just talked today with a EMC representative about the D7 indexing....it will be Lucene/xml database (Xhive).

So I hope it will be better.

So how those migrated indexes will work? Or would it be better to rebuild them?

njain

Let me ask Product Management to respond to this.

Zakusov

So, Xhive has been included to Developer Edition 6.5 SP1 package, hasn't it?

sunilSarje

These are major advantage of ESS over FAST

- NAS Support ( alternate to costly SAN Storage)

- Indexes are compact in size ( saves on storage )

- HA does not need 100% additional server capacity

- One node should be able to search more than 20 million objects

- Lucene based ( widely used / very active developer community )

- In my experience the FAST infrastructure costs is 20% of overall

Check here for consolidated notes prepared by Alexandra from EMC World

http://www.alexandra.st/2009/05/24/emc-world-2009-enterprise-search-server-ess/

DCTM_Guru

Its probably easier to rebuild the index than try to migrate it. Obviously, if you have a lot of content, this make take some time (over the weekend), but there are probably other upgrade/migration issues that are more critical that you should worry about.

RalfKahrl

I don't think you can migrate a Fast index to the new search engine at all. Maybe you can use the already generated fixml to speed up building the new index. But if I recall the presentation at EMCWorld conerning the new Search Server, there will be several migration scenarios available one was running Fast and ESS side by side... Let's wait until the product arrives and see what the provided documentation will tell us ;-)