client/splunk.js
function(fieldName, ranges) {
            if (!this.dataModelObject.hasField(fieldName)) {
                throw new Error("Did not find field " + fieldName);
            }
            var f = this.dataModelObject.fieldByName(fieldName);
            if ("number" !== f.type) {
                throw new Error("Field was of type " + f.type + ", expected number.");
            }

            // In Splunk 6.0.1.1, data models incorrectly expect strings for these fields
            // instead of numbers. In 6.1, this is fixed and both are accepted.
            var updatedRanges = {};
            if (!utils.isUndefined(ranges.start) && ranges.start !== null) {
                updatedRanges.start = ranges.start;
            }
            if (!utils.isUndefined(ranges.end) && ranges.end !== null) {
                updatedRanges.end = ranges.end;
            }
            if (!utils.isUndefined(ranges.step) && ranges.step !== null) {
                updatedRanges.size = ranges.step;
            }
            if (!utils.isUndefined(ranges.limit) && ranges.limit !== null) {
                updatedRanges.maxNumberOf = ranges.limit;
            }

            this.columns.push({
                fieldName: fieldName,
                owner: f.owner,
                type: f.type,
                display: "ranges",
                ranges: updatedRanges
            });

            return this;
        }
function(fieldName, ranges) {
            if (!this.dataModelObject.hasField(fieldName)) {
                throw new Error("Did not find field " + fieldName);
            }
            var f = this.dataModelObject.fieldByName(fieldName);
            if ("number" !== f.type) {
                throw new Error("Field was of type " + f.type + ", expected number.");
            }

            // In Splunk 6.0.1.1, data models incorrectly expect strings for these fields
            // instead of numbers. In 6.1, this is fixed and both are accepted.
            var updatedRanges = {};
            if (!utils.isUndefined(ranges.start) && ranges.start !== null) {
                updatedRanges.start = ranges.start;
            }
            if (!utils.isUndefined(ranges.end) && ranges.end !== null) {
                updatedRanges.end = ranges.end;
            }
            if (!utils.isUndefined(ranges.step) && ranges.step !== null) {
                updatedRanges.size = ranges.step;
            }
            if (!utils.isUndefined(ranges.limit) && ranges.limit !== null) {
                updatedRanges.maxNumberOf = ranges.limit;
            }

            this.columns.push({
                fieldName: fieldName,
                owner: f.owner,
                type: f.type,
                display: "ranges",
                ranges: updatedRanges
            });

            return this;
        }
function ( fieldName , ranges ) { if ( ! this . dataModelObject . hasField ( fieldName ) ) { throw new Error ( "Did not find field " + fieldName ) ; } var f = this . dataModelObject . fieldByName ( fieldName ) ; if ( "number" !== f . type ) { throw new Error ( "Field was of type " + f . type + ", expected number." ) ; } // In Splunk 6.0.1.1, data models incorrectly expect strings for these fields // instead of numbers. In 6.1, this is fixed and both are accepted. var updatedRanges = { } ; if ( ! utils . isUndefined ( ranges . start ) && ranges . start !== null ) { updatedRanges . start = ranges . start ; } if ( ! utils . isUndefined ( ranges . end ) && ranges . end !== null ) { updatedRanges . end = ranges . end ; } if ( ! utils . isUndefined ( ranges . step ) && ranges . step !== null ) { updatedRanges . size = ranges . step ; } if ( ! utils . isUndefined ( ranges . limit ) && ranges . limit !== null ) { updatedRanges . maxNumberOf = ranges . limit ; } this . columns . push ( { fieldName : fieldName , owner : f . owner , type : f . type , display : "ranges" , ranges : updatedRanges } ) ; return this ; }
Add a column split on a numeric field, splitting the values into ranges.

@param {String} fieldName The field to split on.
@param {Object} options An optional dictionary of collection filtering and pagination options:
- `start` (_integer_): The value of the start of the first range, or null to take the lowest value in the events.
- `end` (_integer_): The value for the end of the last range, or null to take the highest value in the events.
- `step` (_integer_): The the width of each range, or null to have Splunk calculate it.
- `limit` (_integer_): The maximum number of ranges to split into, or null for no limit.
@return {splunkjs.Service.PivotSpecification} The updated pivot specification.

@method splunkjs.Service.PivotSpecification
Add a column split on a numeric field splitting the values into ranges .