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

Cannot load list of indexes #1454

Closed
zhugw opened this issue Oct 19, 2017 · 4 comments
Closed

Cannot load list of indexes #1454

zhugw opened this issue Oct 19, 2017 · 4 comments
Assignees
Projects

Comments

@zhugw
Copy link

@zhugw zhugw commented Oct 19, 2017

very strange when I click indexes of a collection -- data_02, it gives me this error info

Cannot load list of indexes.

Error:
Wrong type for field (background) double != 8

but click indexes of other collections is OK.

In addition if I execute getIndexes command explicitly, it is also OK

> db.data_02.getIndexes()
@zhugw
Copy link
Author

@zhugw zhugw commented Oct 21, 2017

Maybe it's caused by this reason , exists invalid value for background key, e.g

	{
		"v" : 1,
		"key" : {
			"importStatus" : 1
		},
		"name" : "importStatus_1",
		"ns" : "foo.data_02",
		"background" : 1 # it should be 'true' not 1
	},
@liitfr
Copy link

@liitfr liitfr commented Oct 27, 2017

Hi ! Same problem here with sparse :

    {
        "v" : 1,
        "unique" : true,
        "key" : {
            "services.twitter.id" : 1
        },
        "name" : "services.twitter.id_1",
        "ns" : "meteor.users",
        "sparse" : 1
    }
]

When trying to list indexes :

Cannot load list of indexes.

Error:
Wrong type for field (sparse) int != 8

simsekgokhan added a commit that referenced this issue Dec 4, 2017
…rror in the related ticket. Solution is to use non-throwing mongo::BSONObj getField* functions instead of throwing BsonUtils functions.
@simsekgokhan
Copy link
Collaborator

@simsekgokhan simsekgokhan commented Dec 4, 2017

Hi @zhugw @liitfr, thanks for reporting the problem.
Both of the issues seem to have the same root cause in the code.
We plan to include the fix with in the next release Robo 3T 1.2.

@simsekgokhan simsekgokhan added this to In-progress in Robo 3T 1.2 Dec 7, 2017
@simsekgokhan simsekgokhan self-assigned this Dec 7, 2017
@simsekgokhan simsekgokhan moved this from In-progress to Fixed in Robo 3T 1.2 Dec 7, 2017
@simsekgokhan simsekgokhan moved this from Fixed to Ready-For-Testing in Robo 3T 1.2 Dec 8, 2017
@simsekgokhan
Copy link
Collaborator

@simsekgokhan simsekgokhan commented Dec 29, 2020

Feel free to re-open if you still have the problem with latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Robo 3T 1.2
Ready-For-Testing
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants