In MDEX Engine 6.1.2, the status of the following Dgraph and Dgidx flags has changed. This topic summarizes all the changes.

The status of the following Dgraph flags has changed:

Flag

Description of change

-A

The -A flag is deprecated and is not guaranteed to be supported in future releases.

The -A flag disallows server shutdown and restart through admin?op=exit and admin?op=restart URL commands sent to the Dgraph.

--explicit_no_keep_alive

The --explicit_no_keep_alive flag is deprecated and if specified triggers a deprecation warning but is otherwise ignored.

In previous releases, this flag instructed the MDEX Engine to include a "Connection: close" HTTP response header to inform clients that connections are closed after completion of each response. This is now the default behavior.

--wildcard_approx

The --wildcard_approx Dgraph flag is deprecated and if specified triggers a deprecation warning but is otherwise ignored.

The MDEX Engine 6.1.2 uses a different mechanism for wildcard search that does not require using this flag.

In previous releases, you could use this flag in some cases to improve performance of wildcard search by allowing approximate wildcard search query matching.

For more information, see the topic "Wildcard simplification" in this guide.

--stat-bins-thresh

The--stat-bins-thresh flag is deprecated and is not guaranteed to be supported in future releases. This flag globally sets the threshold for the maximum number of records above which the MDEX Engine stops computing record counts. By default, the MDEX Engine returns refinement counts for records with no threshold.

If you want to speed up processing and do not need the counts, Oracle recommends using the RECORD_COUNT_DISABLE_THRESHOLD option in the refinement_config.xml file. For more information on this option, see the Performance Tuning Guide.

--stat-bins-cutoff

The --stat-bins-cutoff flag is deprecated and is not guaranteed to be supported in future releases. This flag globally sets the cutoff for record counts.

In cases when you do not need to know the exact counts for dimension values (once they are sufficiently high), Oracle recommends using the MAX_RECORDS_COUNT option in the refinement_config.xml file. For more information on this option, see the Performance Tuning Guide.


Copyright © Legal Notices