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

Endeca MDEX Engine 

GENERAL (6.5.1)

* Release Date: June 2014

* 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.

FEATURES (6.5.1)

Dgraph (6.5.1)

* ECMDEX-46 Added the ability to review the dynamic dictionaries during baseline
  and/or partial updates using the --vocabulary-report option.  For more details
  see the product documentation.

* ECMDEX-49 The Web services and XQuery feature previously depreciated in
  version 6.3 has been removed from the MDEX Engine. This removal includes the 
  MDEX Web service (mdex.xq), the MDEX API through XQuery (or MAXAPI), and any 
  custom Web services based on them. Also, several Dgraph flags that support 
  XQuery are removed. This includes --xquery_fndoc <option>, 
  --xquery_path <directory>, and --disable_web_services.

BUG FIXES (6.5.1)

Dgraph (6.5.1)

* ECIDC-558 (BUG 18299000): When rounding DateTime values down to a QUARTER
  using the TRUNC function of Endeca Analytics, the returned value was incorrect.
  This bug has been fixed.

* ECMDEX-205: The "did you mean" suggestions were computed on ineligible query
  terms. This potential performance issue has been addressed.

* ECMDEX-217: Improved dgraph and eneperf buffer allocation performance during
  large data exchanges.

* ECMDEX-221 (Bug 17557400): Range filter for integer attributes of >0 and <0
  included records with zero value (so the filters acted like >=0 and <=0 
  respectively). This has been fixed.
  
* ECMDEX-225 (Bug 17434738): Oracle Language Technology (OLT) language analysis of
  Norwegian (Bokmal) compounds has been improved.

* ECMDEX-227 (Bug 17468213): An optimization was added to improve response-
  packing performance in certain cases when 5.x packing would outperform 6.x.

* ECMDEX-250 (Bug 17945998): Symbol characters were not being treated as white space 
  when punctuation was also present in the query string.  The bug has been fixed.

* ECMDEX-278 (Bug 18268394): Oracle Language Technology (OLT) language analysis of
  Dutch compounds has been improved.

KNOWN ISSUES (6.5.1)

Dgraph (6.5.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.5.0)

* Release Date: December 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.

FEATURES (6.5.0)

* ECMDEX-69: Oracle Language Technology (OLT) language analysis has
  been upgraded to OLT 1.4 in this release, providing many improvements
  in search accuracy for those languages configured to use OLT.

* ECMDEX-70: International Components for Unicode (ICU) is upgraded to 51.2. 
  Default accent ordering behavior for French changed; backward accent ordering
  was the default for all French locales but is now only applicable to 
  Canadian French (fr-CA). Updates and fixes have been made in the collation 
  of many other languages as well.

BUG FIXES (6.5.0)

Dgraph (6.5.0)

* ECMDEX-142 (Bug 17350281): The amount of memory used by the Stratify relevance ranking
  module has been reduced.

* ECMDEX-180: A timing issue that could potentially lead to a core dump
  during startup has been fixed.

* ECMDEX-191 (Bug 17449628): A latency issue with admin?op=ping queries has been fixed.
  In previous releases, a ping query could be delayed for seconds by the
  completion of a partial update.

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

* ECMDEX-250 (Bug 17945998): Symbol characters were not being treated as white space 
  when punctuation was also present in the query string.  The bug has been fixed.

Dgidx (6.5.0)

* ECMDEX-98 (Bug 16972880): If a DimVal synonym has the same name as its DimVal, 
  ranking by the Freq/WFreq relevancy ranking could be inaccurate.
  Synonyms with a name conflicting with its DimVal are now detected
  by Dgidx and ignored - an error is logged.

* ECMDEX-157 (Bug 17417745): A hang has been fixed in Oracle Language Technology (OLT)
  analysis when tokenizing certain sequences of Chinese characters with
  ambiguous segmentation.  It is unlikely that such sequences would occur
  in natural text.

KNOWN ISSUES (6.5.0)

Dgraph (6.5.0)

* 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 (Bug 16782163): A bug has been fixed that caused an intermittent Dgraph failure
  when Oracle Language Technology (OLT) analysis was used for query processing.

* ECMDEX-77 (Bug 16761103): 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 (Bug 16829040): 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 (Bug 16408975): Oracle Language Technology (OLT) language analysis of
  Swedish compounds has been improved leading to better text search recall
  for Swedish.

* IFCORE-1708 (Bug 16692049): 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 (Bug 15885610): Fixed a bug where dynamically ranked dimension values could 
  cause the Dgraph to fail under some circumstances.

* IFCORE-1667 (Bug 15898079): 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 (Bug 16184278): 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 (Bug 16370239): 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.
  
======================================================================