======================================================================

Endeca MDEX Engine 

GENERAL (6.4.1.2)

* Release Date: September 2013

* The release notes may have been updated since the release date.  
  The latest release notes are available through the Oracle Endeca 
  Commerce documentation page on the Oracle Technology Network at 
  http://www.oracle.com/technetwork/indexes/documentation/endecaguidedsearch-1552767.html 
  or by contacting Oracle Technical Support for Endeca Commerce Products.

BUG FIXES (6.4.1.2)

Dgidx (6.4.1.2)

* ECMDEX-125: Punctuation is no longer indexed when Oracle Language Technology (OLT) analysis 
  is used to process text. The behavior is now consistent with Latin-1 language analysis 
  and fixes problems with spell correction, DYM and automatic phrasing (especially for 
  Japanese nakaguro punctuation).

Dgraph (6.4.1.2)

* IFCORE-1701: Oracle Language Technology (OLT) language analysis of
  Swedish compounds has been further improved.

KNOWN ISSUES (6.4.1.2)

Dgraph (6.4.1.2)

* ECMDEX-67: Possible performance degradation affecting front-end applications
  running on Solaris 11.

  If front-end applications running on Solaris 11 (or above) experience
  one-second jumps in MDEX TCP connect times under load, and do so even after
  running the included tcp_time_wait_tune.sh script (see the Performance Tuning
  Guide, Appendix H, Tuning network performance on Solaris), then they could be
  affected by the introduction of port randomization in Solaris 11.

* IFCORE-1637: A dimension search query with D=* produces results ordered 
  according to the default dimension value ranking, regardless of the value
  of the Dk (Dimension Search Rank) parameter.  Relevance ranking works as
  expected for other types of dimension search queries.

======================================================================

Endeca MDEX Engine 

GENERAL (6.4.1.1)

* Release Date: June 2013

* The release notes may have been updated since the release date.  
  The latest release notes are available through the Oracle Endeca 
  Commerce documentation page on the Oracle Technology Network at 
  http://www.oracle.com/technetwork/indexes/documentation/endecaguidedsearch-1552767.html 
  or by contacting Oracle Technical Support for Endeca Commerce Products.

BUG FIXES (6.4.1.1)

Dgraph (6.4.1.1)

* ECMDEX-75: A bug has been fixed that caused an intermittent Dgraph failure
  when Oracle Language Technology (OLT) analysis was used for query processing.

* ECMDEX-77: Altered MDEX behavior so that if an Experience Manager rule is
  ignored due to a missing dimension value used as the trigger, the MDEX
  publish action proceeds with the valid rules and succeeds instead of failing.

* ECMDEX-82: A bug has been fixed that caused the --thesaurus_cutoff Dgraph
  option to be ignored.

* IFCORE-686: A bug has been fixed that prevented stemming from working
  with the en-GB language code.  Since a default stemming dictionary is 
  not provided for en-GB, a custom stemming dictionary must be configured.

* IFCORE-1701: Oracle Language Technology (OLT) language analysis of
  Swedish compounds has been improved leading to better text search recall
  for Swedish.

* IFCORE-1708: In addition to supporting standard and endeca collations, the
  following collation is now supported for Simplified and Traditional Chinese: 
  pinyin.

Dgidx (6.4.1.1)

* ECMDEX-91: A bug has been fixed that caused excessive logging of messages 
  indicating the successful loading of Oracle Language Technology (OLT) analyzers 
  when Dgidx was run in verbose mode.

KNOWN ISSUES (6.4.1.1)

Dgraph (6.4.1.1)

* ECMDEX-67: Possible performance degradation affecting front-end applications
  running on Solaris 11.

  If front-end applications running on Solaris 11 (or above) experience
  one-second jumps in MDEX TCP connect times under load, and do so even after
  running the included tcp_time_wait_tune.sh script (see the Performance Tuning
  Guide, Appendix H, Tuning network performance on Solaris), then they could be
  affected by the introduction of port randomization in Solaris 11.

* IFCORE-1637: A dimension search query with D=* produces results ordered 
  according to the default dimension value ranking, regardless of the value
  of the Dk (Dimension Search Rank) parameter.  Relevance ranking works as
  expected for other types of dimension search queries.

======================================================================

Endeca MDEX Engine 

GENERAL (6.4.1)

* Release Date: April 2013

* The release notes may have been updated since the release date.  
  The latest release notes are available through the Oracle Endeca 
  Commerce documentation page on the Oracle Technology Network at 
  http://www.oracle.com/technetwork/indexes/documentation/endecaguidedsearch-1552767.html 
  or by contacting Oracle Technical Support for Endeca Commerce Products.

BUG FIXES (6.4.1)

Dgraph (6.4.1)

* IFCORE-1564: Phrased search terms are now supported in FREQ and WFREQ 
  relevance ranking modules. 

* IFCORE-1665: Fixed a bug where dynamically ranked dimension values could 
  cause the Dgraph to fail under some circumstances.

* IFCORE-1667: Fixed a bug where calling mdex:dimension-value-id-from-path() MAX
  with an invalid path could crash the Dgraph. This now throws a catchable 
  exception.

* IFCORE-1686: The --diacritic-folding command line option is now supported
  for Oracle Language Technology (OLT) as well as Latin-1 language analysis.
  And the Orthographic Normalization provided by OLT language analysis has
  been improved for German.

* IFCORE-1695: Fixed a bug in proximity search (i.e. NEAR and ONEAR)
  when both arguments are the same.

* IFCORE-1696: If a search term with interior punctuation, e.g. Biondi-Santi,
  occurred in a boolean query and was followed by a ")" without intervening
  spaces, the query failed with a parse error.  This has been fixed.

KNOWN ISSUES (6.4.1)

Dgraph (6.4.1)

* IFCORE-1637: A dimension search query with D=* produces results ordered 
  according to the default dimension value ranking, regardless of the value
  of the Dk (Dimension Search Rank) parameter.  Relevance ranking works as
  expected for other types of dimension search queries.

======================================================================

Endeca MDEX Engine 

GENERAL (6.4.0) 

* Release Date: December 2012

BUG FIXES (6.4.0)

Dgraph (6.4.0)

* IFCORE-1053: The Dgraph incorrectly indicated that updates are reflected in
  the dataStore for failed partial updates.

* IFCORE-1598: Merch rules: provide the ability for firing on specific
  dimension values (aka "only at this location"), independent of search terms
  being provided for the rule

  To provide this ability, a new "PROHIBITED" attribute has been added to
  the "KEYWORD" subelement of the "MERCH_RULE_TRIGGER" element. When
  PROHIBITED="TRUE", a query must explicitly not contain a text search as
  part of satisfying the trigger.

Dgidx (6.4.0)

* IFCORE-1911: Suppress Dgidx WARN messages in non-verbose mode. When there is
  a warning or notification during indexing, the default behavior now only
  outputs record IDs instead of full records. Full records can be re-enabled by
  enabling the --printFullRecords flag.

KNOWN ISSUES (6.4.0)

Dgraph (6.4.0)

* IFCORE-1637: A dimension search query with D=* produces results ordered 
  according to the default dimension value ranking, regardless of the value
  of the Dk (Dimension Search Rank) parameter.  Relevance ranking works as
  expected for other types of dimension search queries.
  
======================================================================