Solr not able to get max(id)











up vote
0
down vote

favorite












I am new to Apache Solr and I am using 7.5 I have created a collection TestCollection with 2 fields id and name, id's default datatype is taken as string and the name's datatype is string.



I have indexed records by using curl and I have indexed id up to 400000 but when I give



http://127.0.0.1:8983/solr/TestCollection/select?json.facet={maxid:max(id)}&q=*:*&rows=0 


I get as maxid as 99999



facets: {
count: 495798,
maxid: "99999"
}


What is the mistake that I am making is it with the data type.










share|improve this question






















  • try the link...wiki.apache.org/solr/StatsComponent...you may need to change the type of id field...currently you have it as string...you may need to change it to integer
    – Abhijit Bashetti
    Nov 12 at 6:27















up vote
0
down vote

favorite












I am new to Apache Solr and I am using 7.5 I have created a collection TestCollection with 2 fields id and name, id's default datatype is taken as string and the name's datatype is string.



I have indexed records by using curl and I have indexed id up to 400000 but when I give



http://127.0.0.1:8983/solr/TestCollection/select?json.facet={maxid:max(id)}&q=*:*&rows=0 


I get as maxid as 99999



facets: {
count: 495798,
maxid: "99999"
}


What is the mistake that I am making is it with the data type.










share|improve this question






















  • try the link...wiki.apache.org/solr/StatsComponent...you may need to change the type of id field...currently you have it as string...you may need to change it to integer
    – Abhijit Bashetti
    Nov 12 at 6:27













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am new to Apache Solr and I am using 7.5 I have created a collection TestCollection with 2 fields id and name, id's default datatype is taken as string and the name's datatype is string.



I have indexed records by using curl and I have indexed id up to 400000 but when I give



http://127.0.0.1:8983/solr/TestCollection/select?json.facet={maxid:max(id)}&q=*:*&rows=0 


I get as maxid as 99999



facets: {
count: 495798,
maxid: "99999"
}


What is the mistake that I am making is it with the data type.










share|improve this question













I am new to Apache Solr and I am using 7.5 I have created a collection TestCollection with 2 fields id and name, id's default datatype is taken as string and the name's datatype is string.



I have indexed records by using curl and I have indexed id up to 400000 but when I give



http://127.0.0.1:8983/solr/TestCollection/select?json.facet={maxid:max(id)}&q=*:*&rows=0 


I get as maxid as 99999



facets: {
count: 495798,
maxid: "99999"
}


What is the mistake that I am making is it with the data type.







apache solr






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 at 6:09









Vijayanand Premnath

78221231




78221231












  • try the link...wiki.apache.org/solr/StatsComponent...you may need to change the type of id field...currently you have it as string...you may need to change it to integer
    – Abhijit Bashetti
    Nov 12 at 6:27


















  • try the link...wiki.apache.org/solr/StatsComponent...you may need to change the type of id field...currently you have it as string...you may need to change it to integer
    – Abhijit Bashetti
    Nov 12 at 6:27
















try the link...wiki.apache.org/solr/StatsComponent...you may need to change the type of id field...currently you have it as string...you may need to change it to integer
– Abhijit Bashetti
Nov 12 at 6:27




try the link...wiki.apache.org/solr/StatsComponent...you may need to change the type of id field...currently you have it as string...you may need to change it to integer
– Abhijit Bashetti
Nov 12 at 6:27












1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










As Abhijit mentions in the comment, change your field type.



A string field that starts with "9" will always be larger than (sort after) one that starts with 4. This is the same as Z being sorted after A, as it's considered "larger". When using strings their sort order is based on each character by itself and not the "whole string".



Change the field type to a plong field and reindex your content, and both sorting and max would work as you expact it to do.






share|improve this answer





















    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',
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53256697%2fsolr-not-able-to-get-maxid%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote



    accepted










    As Abhijit mentions in the comment, change your field type.



    A string field that starts with "9" will always be larger than (sort after) one that starts with 4. This is the same as Z being sorted after A, as it's considered "larger". When using strings their sort order is based on each character by itself and not the "whole string".



    Change the field type to a plong field and reindex your content, and both sorting and max would work as you expact it to do.






    share|improve this answer

























      up vote
      1
      down vote



      accepted










      As Abhijit mentions in the comment, change your field type.



      A string field that starts with "9" will always be larger than (sort after) one that starts with 4. This is the same as Z being sorted after A, as it's considered "larger". When using strings their sort order is based on each character by itself and not the "whole string".



      Change the field type to a plong field and reindex your content, and both sorting and max would work as you expact it to do.






      share|improve this answer























        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        As Abhijit mentions in the comment, change your field type.



        A string field that starts with "9" will always be larger than (sort after) one that starts with 4. This is the same as Z being sorted after A, as it's considered "larger". When using strings their sort order is based on each character by itself and not the "whole string".



        Change the field type to a plong field and reindex your content, and both sorting and max would work as you expact it to do.






        share|improve this answer












        As Abhijit mentions in the comment, change your field type.



        A string field that starts with "9" will always be larger than (sort after) one that starts with 4. This is the same as Z being sorted after A, as it's considered "larger". When using strings their sort order is based on each character by itself and not the "whole string".



        Change the field type to a plong field and reindex your content, and both sorting and max would work as you expact it to do.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 at 10:49









        MatsLindh

        24.6k22240




        24.6k22240






























            draft saved

            draft discarded




















































            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


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




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53256697%2fsolr-not-able-to-get-maxid%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            Xamarin.iOS Cant Deploy on Iphone

            Glorious Revolution

            Dulmage-Mendelsohn matrix decomposition in Python