Cosmosdb index precision for fixed value strings
I want to index over a field in a collection whose values can be only 4 characters long
{ "field": "abcd" }
Can I use an index precision of 4 like below to save on RU's without having any side effects?
"indexes": [
{
"kind": "Range",
"dataType": "String",
"precision": 4
},
]
indexing
azure-cosmosdb asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
add a comment |
I want to index over a field in a collection whose values can be only 4 characters long
{ "field": "abcd" }
Can I use an index precision of 4 like below to save on RU's without having any side effects?
"indexes": [
{
"kind": "Range",
"dataType": "String",
"precision": 4
},
]
indexing
azure-cosmosdb asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
add a comment |
I want to index over a field in a collection whose values can be only 4 characters long
{ "field": "abcd" }
Can I use an index precision of 4 like below to save on RU's without having any side effects?
"indexes": [
{
"kind": "Range",
"dataType": "String",
"precision": 4
},
]
indexing
azure-cosmosdb asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
I want to index over a field in a collection whose values can be only 4 characters long
{ "field": "abcd" }
Can I use an index precision of 4 like below to save on RU's without having any side effects?
"indexes": [
{
"kind": "Range",
"dataType": "String",
"precision": 4
},
]
indexing
azure-cosmosdb indexing
azure-cosmosdb asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
asked Nov 20 '18 at 0:33
tariq zafartariq zafar
345214
345214
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
For Range indexes, the index term length will never exceed the actual string length. So,if all of your strings are 4 characters long, then this will not have any impact (neither positive or negative). You're better off, however, to set the precision to -1 so that we don't have to change your index policy in the future in case the length of the strings changes.
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
Thanks for answering. Out of curiosity, will we have considerable savings in terms of RUs if we used smaller precision to save indices? Can you just give some figures?
– tariq zafar
Nov 20 '18 at 1:23
I am from the CosmosDB engineering team. The precision of the term does not have an impact on the RU cost per term. Roughly the RU cost corresponds to cost of writing the document (which depends on the size of the document) and the number of terms produced during analysis of the document. If you want to reduce the RU cost of your writes, you should exclude all paths that you don't need to index from your indexing policy.
– Krishnan Sundaram
Dec 9 '18 at 5:42
add a comment |
Based on this official statement, the choice of the index precision might affect the performance of string range queries. Obviously, there is no specific statements about
effect like hash type index. So,I suggest you do actual test based on the simulation data instead so that maybe you could find the truth.
BTW, if you want to perform ORDER BY queries against your string properties, you must specify a precision of -1 for the corresponding paths.
There are more documents about saving RUs for your reference.
1.https://lbadri.wordpress.com/2018/04/07/is-azure-cosmos-db-really-expensive/
2.https://medium.com/@thomasweiss_io/how-i-learned-to-stop-worrying-and-love-cosmos-dbs-request-units-92c68c62c938
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53384586%2fcosmosdb-index-precision-for-fixed-value-strings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
For Range indexes, the index term length will never exceed the actual string length. So,if all of your strings are 4 characters long, then this will not have any impact (neither positive or negative). You're better off, however, to set the precision to -1 so that we don't have to change your index policy in the future in case the length of the strings changes.
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
Thanks for answering. Out of curiosity, will we have considerable savings in terms of RUs if we used smaller precision to save indices? Can you just give some figures?
– tariq zafar
Nov 20 '18 at 1:23
I am from the CosmosDB engineering team. The precision of the term does not have an impact on the RU cost per term. Roughly the RU cost corresponds to cost of writing the document (which depends on the size of the document) and the number of terms produced during analysis of the document. If you want to reduce the RU cost of your writes, you should exclude all paths that you don't need to index from your indexing policy.
– Krishnan Sundaram
Dec 9 '18 at 5:42
add a comment |
For Range indexes, the index term length will never exceed the actual string length. So,if all of your strings are 4 characters long, then this will not have any impact (neither positive or negative). You're better off, however, to set the precision to -1 so that we don't have to change your index policy in the future in case the length of the strings changes.
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
Thanks for answering. Out of curiosity, will we have considerable savings in terms of RUs if we used smaller precision to save indices? Can you just give some figures?
– tariq zafar
Nov 20 '18 at 1:23
I am from the CosmosDB engineering team. The precision of the term does not have an impact on the RU cost per term. Roughly the RU cost corresponds to cost of writing the document (which depends on the size of the document) and the number of terms produced during analysis of the document. If you want to reduce the RU cost of your writes, you should exclude all paths that you don't need to index from your indexing policy.
– Krishnan Sundaram
Dec 9 '18 at 5:42
add a comment |
For Range indexes, the index term length will never exceed the actual string length. So,if all of your strings are 4 characters long, then this will not have any impact (neither positive or negative). You're better off, however, to set the precision to -1 so that we don't have to change your index policy in the future in case the length of the strings changes.
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
For Range indexes, the index term length will never exceed the actual string length. So,if all of your strings are 4 characters long, then this will not have any impact (neither positive or negative). You're better off, however, to set the precision to -1 so that we don't have to change your index policy in the future in case the length of the strings changes.
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
answered Nov 20 '18 at 1:15
Samer BoshraSamer Boshra
43924
43924
Thanks for answering. Out of curiosity, will we have considerable savings in terms of RUs if we used smaller precision to save indices? Can you just give some figures?
– tariq zafar
Nov 20 '18 at 1:23
I am from the CosmosDB engineering team. The precision of the term does not have an impact on the RU cost per term. Roughly the RU cost corresponds to cost of writing the document (which depends on the size of the document) and the number of terms produced during analysis of the document. If you want to reduce the RU cost of your writes, you should exclude all paths that you don't need to index from your indexing policy.
– Krishnan Sundaram
Dec 9 '18 at 5:42
add a comment |
Thanks for answering. Out of curiosity, will we have considerable savings in terms of RUs if we used smaller precision to save indices? Can you just give some figures?
– tariq zafar
Nov 20 '18 at 1:23
I am from the CosmosDB engineering team. The precision of the term does not have an impact on the RU cost per term. Roughly the RU cost corresponds to cost of writing the document (which depends on the size of the document) and the number of terms produced during analysis of the document. If you want to reduce the RU cost of your writes, you should exclude all paths that you don't need to index from your indexing policy.
– Krishnan Sundaram
Dec 9 '18 at 5:42
Thanks for answering. Out of curiosity, will we have considerable savings in terms of RUs if we used smaller precision to save indices? Can you just give some figures?
– tariq zafar
Nov 20 '18 at 1:23
Thanks for answering. Out of curiosity, will we have considerable savings in terms of RUs if we used smaller precision to save indices? Can you just give some figures?
– tariq zafar
Nov 20 '18 at 1:23
I am from the CosmosDB engineering team. The precision of the term does not have an impact on the RU cost per term. Roughly the RU cost corresponds to cost of writing the document (which depends on the size of the document) and the number of terms produced during analysis of the document. If you want to reduce the RU cost of your writes, you should exclude all paths that you don't need to index from your indexing policy.
– Krishnan Sundaram
Dec 9 '18 at 5:42
I am from the CosmosDB engineering team. The precision of the term does not have an impact on the RU cost per term. Roughly the RU cost corresponds to cost of writing the document (which depends on the size of the document) and the number of terms produced during analysis of the document. If you want to reduce the RU cost of your writes, you should exclude all paths that you don't need to index from your indexing policy.
– Krishnan Sundaram
Dec 9 '18 at 5:42
add a comment |
Based on this official statement, the choice of the index precision might affect the performance of string range queries. Obviously, there is no specific statements about
effect like hash type index. So,I suggest you do actual test based on the simulation data instead so that maybe you could find the truth.
BTW, if you want to perform ORDER BY queries against your string properties, you must specify a precision of -1 for the corresponding paths.
There are more documents about saving RUs for your reference.
1.https://lbadri.wordpress.com/2018/04/07/is-azure-cosmos-db-really-expensive/
2.https://medium.com/@thomasweiss_io/how-i-learned-to-stop-worrying-and-love-cosmos-dbs-request-units-92c68c62c938
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
add a comment |
Based on this official statement, the choice of the index precision might affect the performance of string range queries. Obviously, there is no specific statements about
effect like hash type index. So,I suggest you do actual test based on the simulation data instead so that maybe you could find the truth.
BTW, if you want to perform ORDER BY queries against your string properties, you must specify a precision of -1 for the corresponding paths.
There are more documents about saving RUs for your reference.
1.https://lbadri.wordpress.com/2018/04/07/is-azure-cosmos-db-really-expensive/
2.https://medium.com/@thomasweiss_io/how-i-learned-to-stop-worrying-and-love-cosmos-dbs-request-units-92c68c62c938
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
add a comment |
Based on this official statement, the choice of the index precision might affect the performance of string range queries. Obviously, there is no specific statements about
effect like hash type index. So,I suggest you do actual test based on the simulation data instead so that maybe you could find the truth.
BTW, if you want to perform ORDER BY queries against your string properties, you must specify a precision of -1 for the corresponding paths.
There are more documents about saving RUs for your reference.
1.https://lbadri.wordpress.com/2018/04/07/is-azure-cosmos-db-really-expensive/
2.https://medium.com/@thomasweiss_io/how-i-learned-to-stop-worrying-and-love-cosmos-dbs-request-units-92c68c62c938
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
Based on this official statement, the choice of the index precision might affect the performance of string range queries. Obviously, there is no specific statements about
effect like hash type index. So,I suggest you do actual test based on the simulation data instead so that maybe you could find the truth.
BTW, if you want to perform ORDER BY queries against your string properties, you must specify a precision of -1 for the corresponding paths.
There are more documents about saving RUs for your reference.
1.https://lbadri.wordpress.com/2018/04/07/is-azure-cosmos-db-really-expensive/
2.https://medium.com/@thomasweiss_io/how-i-learned-to-stop-worrying-and-love-cosmos-dbs-request-units-92c68c62c938
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
answered Nov 20 '18 at 2:06
Jay GongJay Gong
8,9001512
8,9001512
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53384586%2fcosmosdb-index-precision-for-fixed-value-strings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
