Repository: ignite Updated Branches: refs/heads/ignite-2612 a86fdc003 -> 400203743
IGNITE-843 Updated tip for idMapper and nameMapper. Project: http://git-wip-us.apache.org/repos/asf/ignite/repo Commit: http://git-wip-us.apache.org/repos/asf/ignite/commit/6a9ced4a Tree: http://git-wip-us.apache.org/repos/asf/ignite/tree/6a9ced4a Diff: http://git-wip-us.apache.org/repos/asf/ignite/diff/6a9ced4a Branch: refs/heads/ignite-2612 Commit: 6a9ced4ad50061ee24878c7eaf76e041ae2acc25 Parents: 3655140 Author: AKuznetsov <akuznet...@gridgain.com> Authored: Thu Feb 18 20:39:36 2016 +0700 Committer: AKuznetsov <akuznet...@gridgain.com> Committed: Thu Feb 18 20:39:36 2016 +0700 ---------------------------------------------------------------------- .../modules/states/configuration/clusters/binary.jade | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/ignite/blob/6a9ced4a/modules/control-center-web/src/main/js/app/modules/states/configuration/clusters/binary.jade ---------------------------------------------------------------------- diff --git a/modules/control-center-web/src/main/js/app/modules/states/configuration/clusters/binary.jade b/modules/control-center-web/src/main/js/app/modules/states/configuration/clusters/binary.jade index 60e34db..6e78df3 100644 --- a/modules/control-center-web/src/main/js/app/modules/states/configuration/clusters/binary.jade +++ b/modules/control-center-web/src/main/js/app/modules/states/configuration/clusters/binary.jade @@ -32,8 +32,8 @@ form.panel.panel-default(name='binary' novalidate) ignite-form-field-label | ID mapper: ignite-form-field-tooltip - | Type and field ID mapper for binary objects#[br] - | Ignite never writes full strings for field or type names. Instead, for performance reasons, Ignite writes integer hash codes for type and field names. It has been tested that hash code conflicts for the type names or the field names within the same type are virtually non-existent and, to gain performance, it is safe to work with hash codes. For the cases when hash codes for different types or fields actually do collide #[b BinaryIdMapper] allows to override the automatically generated hash code IDs for the type and field names + | Maps given from BinaryNameMapper type and filed name to ID that will be used by Ignite in internals#[br] + | Ignite never writes full strings for field or type names. Instead, for performance reasons, Ignite writes integer hash codes for type/class and field names. It has been tested that hash code conflicts for the type/class names or the field names within the same type are virtually non-existent and, to gain performance, it is safe to work with hash codes. For the cases when hash codes for different types or fields actually do collide #[b BinaryIdMapper] allows to override the automatically generated hash code IDs for the type and field names ignite-form-field-java-class( data-id='idMapper' data-name='idMapper' @@ -44,7 +44,7 @@ form.panel.panel-default(name='binary' novalidate) ignite-form-field-label | Name mapper: ignite-form-field-tooltip - | Name mapper + | Maps type/class and field names to different names#[br] ignite-form-field-java-class( data-id='nameMapper' data-name='nameMapper' @@ -94,8 +94,8 @@ form.panel.panel-default(name='binary' novalidate) ignite-form-field-label | ID mapper: ignite-form-field-tooltip - | Type and field ID mapper for binary objects#[br] - | Ignite never writes full strings for field or type names. Instead, for performance reasons, Ignite writes integer hash codes for type and field names. It has been tested that hash code conflicts for the type names or the field names within the same type are virtually non-existent and, to gain performance, it is safe to work with hash codes. For the cases when hash codes for different types or fields actually do collide #[b BinaryIdMapper] allows to override the automatically generated hash code IDs for the type and field names + | Maps given from BinaryNameMapper type and filed name to ID that will be used by Ignite in internals#[br] + | Ignite never writes full strings for field or type/class names. Instead, for performance reasons, Ignite writes integer hash codes for type/class and field names. It has been tested that hash code conflicts for the type/class names or the field names within the same type are virtually non-existent and, to gain performance, it is safe to work with hash codes. For the cases when hash codes for different types or fields actually do collide #[b BinaryIdMapper] allows to override the automatically generated hash code IDs for the type and field names ignite-form-field-java-class( data-id='idMapper' data-name='idMapper' @@ -106,7 +106,7 @@ form.panel.panel-default(name='binary' novalidate) ignite-form-field-label | Name mapper: ignite-form-field-tooltip - | Name mapper + | Maps type/class and field names to different names#[br] ignite-form-field-java-class( data-id='nameMapper' data-name='nameMapper'
