Elasticsearch: Client API should use String instead of Text

Created on 4 Jan 2016  路  6Comments  路  Source: elastic/elasticsearch

For similar reasons to #15729, our client API should use the well-known String class where it today uses Text.

:CorFeatureJava High Level REST Client >enhancement CorFeatures help wanted
Source
picture jpountz

Most helpful comment

I think that this is still valid given that the Java high level REST client is reusing the java api classes. Would be nice to not use anything that depends on lucene in there.

picture javanna on 13 Mar 2017
👍2

All 6 comments

Hi, I am new to OSS but I would like to have a go at resolving this issue

Jordanwmk picture Jordanwmk on 13 Mar 2017

Since we're moving away from the TransportClient in general I don't think this is a good on. Honestly we should probably close this one in anticipation of https://github.com/elastic/elasticsearch/issues/23331

nik9000 picture nik9000 on 13 Mar 2017

@jpountz, what do you think about closing this?

nik9000 picture nik9000 on 13 Mar 2017

I think that this is still valid given that the Java high level REST client is reusing the java api classes. Would be nice to not use anything that depends on lucene in there.

javanna picture javanna on 13 Mar 2017
👍2

Pinging @elastic/es-core-infra

elasticmachine picture elasticmachine on 13 Mar 2018

I agree. We should do this. I wonder if we should wait on doing this for a while because it is another breaking change. At some point we'll be asking people to shift to the high level REST client and that is enough breaking change.

nik9000 picture nik9000 on 13 Mar 2018
Was this page helpful?
0 / 5 - 0 ratings

Related issues

brwe picture brwe  路  3Comments
rbayliss picture rbayliss  路  3Comments
Praveen82 picture Praveen82  路  3Comments
ppf2 picture ppf2  路  3Comments
clintongormley picture clintongormley  路  3Comments