I recently spent some cycles building my first POC for a potential customer with OEID v3.0. After running some of the unstructured data through the text enrichment component, I noticed something odd:
For almost a decade, the core Endeca MDEX engine that underpins Oracle Endeca Information Discovery (OEID) has supported one-time indexing (often referred to as a Baseline Update) as well as incremental updates (often referred to as partials). Through all of the incarnations of this functionality, from "partial update pipelines" to "continuous query", there was one common limitation. Your update operations were always limited to act on "per-record" operations.
If you're a person coming from a SQL/RDBMS background, this was a huge limitation and forced a conceptual change in the way that you think about data. Obviously, Endeca is not (and never was) a relational system but the freedom to update data whenever and where ever you please, that SQL provided, was often a pretty big limitation, especially at scale. Building an index nightly for 100,000 E-Commerce products is no big deal. Running a daily process to feed 1 million updated records into a 30 million record Endeca Server instance just so that a set of warranty claims could be "aged" from current month to prior month is something completely different.
Thankfully, with the release of the latest set of components for the ETL layer of OEID (called OEID Integrator), huge changes have been made to the interactions available for modifying an Endeca Server instance (now called a "Data Domain"). If you've longed for a "SQL-style experience" where records can be updated or deleted from a data store by almost any criteria imaginable, OEID Integrator v3.0 delivers.
Adjectives like "agile" and "self-service" have long been used to describe approaches to BI that enable organizations to ask their own questions and produce their own answers. Applied to both processes and products, these labels are applicable any time an organization can relax the "IT bottleneck". Over the past decade, the core tenets of the Endeca vision ("no data left behind, ease of use, and agile delivery") have shaped a product that has empowered organizations to unlock insights in their enterprise data in ways never before possible while simultaneously reducing their reliance on IT to do so. Notice I said "reduce" their reliance, not "eliminate".
Guided Navigation has been the foundation, the rock upon which Endeca (now Oracle Endeca Information Discovery) has based its entire value proposition for the past decade. As a result, it has been the one area of the product that has seen the least amount of change. With the release of Oracle Endeca Information Discovery (OEID) v3.0, Guided Navigation has gotten not an overhaul, but certainly a facelift for the first time that we can recall, making this an exciting time to be on the cutting edge with this software.
Internationalization in Endeca Server
With the release of Endeca Server 7.5.1, the MDEX engine takes a huge leap forward when it comes to supporting a wide variety of languages for Data Discovery applications. The new version supports 22 languages, up from 7 in the previous version. Supporting these new languages is a huge step forward, but the way in which langauages are implemented and supported inside of Endeca Server is what makes this such a big deal.
The first in a series of "mini-posts" detailing new functionality in Oracle Endeca Information Discovery 3.0 - Today: Attribute Based Navigation Configuration
As mentioned last week, there are enhancements both great and small coming in OEID 3.0. None smaller (and proportionally greater) than the ability to select individual attributes in your guided navigation configuration, rather than attribute groups.
A few days ago, Oracle invited us over to their offices for a sneak preview of the latest release of Oracle Endeca Information Discovery (OEID). The OEID 3.0 release will be made available to the public later this year and it's jam-packed with exciting enhancements across all areas of the product.