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

EasyJson compatibility issue #1683

Open
shivamnutanix opened this issue Feb 2, 2024 · 0 comments
Open

EasyJson compatibility issue #1683

shivamnutanix opened this issue Feb 2, 2024 · 0 comments

Comments

@shivamnutanix
Copy link

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.

Error message indicates a compatibility issue between the elastic/v7 package and the easysafe dependency I am using, and I on latest stable easyjson.


/root/.go/pkg/mod/github.com/olivere/elastic/v7@v7.0.32/bulk_create_request_easyjson.go:31:13: in.UnsafeFieldName undefined (type *jlexer.Lexer has no field or method UnsafeFieldName)

/root/.go/pkg/mod/github.com/olivere/elastic/v7@v7.0.32/bulk_delete_request_easyjson.go:31:13: in.UnsafeFieldName undefined (type *jlexer.Lexer has no field or method UnsafeFieldName)

/root/.go/pkg/mod/github.com/olivere/elastic/v7@v7.0.32/bulk_index_request_easyjson.go:31:13: in.UnsafeFieldName undefined (type *jlexer.Lexer has no field or method UnsafeFieldName)

/root/.go/pkg/mod/github.com/olivere/elastic/v7@v7.0.32/bulk_update_request_easyjson.go:31:13: in.UnsafeFieldName undefined (type *jlexer.Lexer has no field or method UnsafeFieldName)

/root/.go/pkg/mod/github.com/olivere/elastic/v7@v7.0.32/bulk_update_request_easyjson.go:230:13: in.UnsafeFieldName undefined (type *jlexer.Lexer has no field or method UnsafeFieldName)```

### Which version of Elastic are you using?

[*] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)

### Please describe the expected behavior
Build to work

### Please describe the actual behavior


### Any steps to reproduce the behavior?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant