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

ElasticsearchIllegalStateException when invoking _cat plugins #5715

Closed
ppf2 opened this issue Apr 7, 2014 · 5 comments
Closed

ElasticsearchIllegalStateException when invoking _cat plugins #5715

ppf2 opened this issue Apr 7, 2014 · 5 comments

Comments

@ppf2
Copy link
Member

ppf2 commented Apr 7, 2014

Reproducible using ES 1.1.0.
/_cat/plugins works fine when no plugins are installed. But once a plugin is installed (eg. latest marvel), it throws an exception indicating that the resulting table constructed has 7 fields in the header row but not enough fields in the data rows to make it a valid table.

{
"status" : 500,
"error" : "ElasticsearchIllegalStateException[mismatch on number of cells 6 in a row compared to header 7]"
}

@dadoonet
Copy link
Member

dadoonet commented Apr 7, 2014

Thanks for reporting it. Will push a fix.

@dadoonet dadoonet self-assigned this Apr 7, 2014
@dadoonet
Copy link
Member

dadoonet commented Apr 7, 2014

Could you list which plugins / versions do you have?

@ppf2
Copy link
Member Author

ppf2 commented Apr 7, 2014

I applied the latest marvel earlier today and the jar version downloaded is
marvel-1.1.0.jar

On Mon, Apr 7, 2014 at 3:05 PM, David Pilato notifications@github.comwrote:

Could you list which plugins / versions do you have?

Reply to this email directly or view it on GitHubhttps://github.com//issues/5715#issuecomment-39789716
.

@dadoonet
Copy link
Member

dadoonet commented Apr 8, 2014

I found it! Thanks for reporting. Actually this issue was introduced by this commit c34d8bd. The header was not updated with this change.

Going to push a fix on 1.1 branch. Other branches are not concerned by this issue.

dadoonet added a commit that referenced this issue Apr 8, 2014
Reproducible using ES 1.1.0.

`/_cat/plugins` works fine when no plugins are installed.

But once a plugin is installed (eg. latest marvel), it throws an exception indicating that the resulting table constructed has 7 fields in the header row but not enough fields in the data rows to make it a valid table.

```
{
  "status" : 500,
  "error" : "ElasticsearchIllegalStateException[mismatch on number of cells 6 in a row compared to header 7]"
}
```

This issue has been introduced when we removed `isolation` feature in 1.1 branch. See c34d8bd.

Closes #5715
@dadoonet
Copy link
Member

dadoonet commented Apr 8, 2014

Closed by abc453d

@dadoonet dadoonet closed this as completed Apr 8, 2014
dadoonet added a commit that referenced this issue Apr 11, 2014
Reproducible using ES 1.1.0.

`/_cat/plugins` works fine when no plugins are installed.

But once a plugin is installed (eg. latest marvel), it throws an exception indicating that the resulting table constructed has 7 fields in the header row but not enough fields in the data rows to make it a valid table.

```
{
  "status" : 500,
  "error" : "ElasticsearchIllegalStateException[mismatch on number of cells 6 in a row compared to header 7]"
}
```

This issue has been introduced when we removed `isolation` feature in 1.1 branch. See c34d8bd.

Closes #5715

(cherry picked from commit abc453d)
@clintongormley clintongormley added the :Data Management/CAT APIs Text APIs behind /_cat label Jun 7, 2015
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
Reproducible using ES 1.1.0.

`/_cat/plugins` works fine when no plugins are installed.

But once a plugin is installed (eg. latest marvel), it throws an exception indicating that the resulting table constructed has 7 fields in the header row but not enough fields in the data rows to make it a valid table.

```
{
  "status" : 500,
  "error" : "ElasticsearchIllegalStateException[mismatch on number of cells 6 in a row compared to header 7]"
}
```

This issue has been introduced when we removed `isolation` feature in 1.1 branch. See c34d8bd.

Closes elastic#5715
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants