Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

indexStatus returns too many indexes in 2.1 #4868

Closed
danielmewes opened this issue Sep 21, 2015 · 2 comments
Closed

indexStatus returns too many indexes in 2.1 #4868

danielmewes opened this issue Sep 21, 2015 · 2 comments
Assignees
@danielmewes
Labels
tp:bug
Milestone
2.1.5

Comments

@danielmewes
Copy link
Member

I have a table t1 with two indexes a and b.

r.table('t1').indexStatus('a')
[
    {
        "function": <binary, 100 bytes, "24 72 65 71 6c 5f..."> ,
        "geo": false ,
        "index": "a" ,
        "multi": false ,
        "outdated": false ,
        "ready": true
    } ,
    {
        "function": <binary, 100 bytes, "24 72 65 71 6c 5f..."> ,
        "geo": false ,
        "index": "b" ,
        "multi": false ,
        "outdated": false ,
        "ready": true
    }
]
r.table('t1').indexStatus('b')
[
    {
        "function": <binary, 100 bytes, "24 72 65 71 6c 5f..."> ,
        "geo": false ,
        "index": "b" ,
        "multi": false ,
        "outdated": false ,
        "ready": true
    }
]

As you can see when I query for the index status for index "a", indexStatus also returns the status of "b". When I query for "b", it works as expected.

This used to work in 2.0.x
@danielmewes danielmewes added this to the 2.1.x milestone Sep 21, 2015
@danielmewes danielmewes self-assigned this Sep 23, 2015
danielmewes pushed a commit that referenced this issue Sep 23, 2015
Fix #4868.
76fcbc4 
Extra indexes reported in index_status result.
@danielmewes
Copy link
Member Author

A fix is up in review 3243

danielmewes pushed a commit that referenced this issue Sep 23, 2015
Fix #4868.
5360eb5 
Extra indexes reported in index_status result.
@danielmewes
Copy link
Member Author

Fixed in next b98848f and v2.1.x 5360eb5

@danielmewes danielmewes modified the milestones: 2.1.x, 2.1.5 Oct 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danielmewes danielmewes

Labels
tp:bug
Projects
None yet
Milestone
2.1.5
Development

No branches or pull requests
1 participant
@danielmewes