Upgrade 7 -> 8. depreciation messages -- ruby api

[Russell_Fulton]

I am about to attempt to upgrade my test system from 7.17 to the latest 8.x...

I have custom written ingestion processes which uses the ruby elasticsearch gem.

Migration assistant says all is good but when I look at the depreciation logs I see:

[2021-08-15T03:57:06,797][DEPRECATION][o.e.d.a.b.BulkRequestParser] [secesprd01] [types removal] Specifying types in bulk requests is deprecated.
[2021-08-15T03:57:07,000][DEPRECATION][o.e.d.a.b.BulkRequestParser] [secesprd01] [types removal] Specifying types in bulk requests is deprecated.
[2021-08-15T03:57:07,028][DEPRECATION][o.e.d.a.b.BulkRequestParser] [secesprd01] [types removal] Specifying types in bulk requests is deprecated.
[2021-08-15T03:57:07,050][DEPRECATION][o.e.d.a.b.BulkRequestParser] [secesprd01] [types removal] Specifying types in bulk requests is deprecated.
[2021-08-15T03:57:07,106][DEPRECATION][o.e.d.a.b.BulkRequestParser] [secesprd01] [types removal] Specifying types in bulk requests is deprecated.
[2021-08-15T03:57:07,167][DEPRECATION][o.e.d.a.b.BulkRequestParser] [secesprd01] [types removal] Specifying types in bulk requests is deprecated.
[2021-08-15T03:57:07,253][DEPRECATION][o.e.d.a.b.BulkRequestParser] [secesprd01] [types removal] Specifying types in bulk requests is deprecated.
[2021-08-15T03:57:07,266][DEPRECATION][o.e.d.r.a.d.RestDeleteAction] [secesprd01] [types removal] Specifying types in document index requests is deprecated, use the typeless endpoints instead (/{index}/_doc/{id}, /{index}/_doc, or /{index}/_create/{id}).

when I migrated from 6 to 7 i removed all references to type in my code and at the time I noted that this made no difference to the depreciation warings.

Are these warning because the 7.x ruby gem specifies type even when the api call does not?

I also see warning about access to system indexes -- these are all from kibana. I take it these will be fixed with the version 8 kibana.

[willemdh]

Hello @Russell_Fulton,

Not sure if it applies here, but I have seen multiple cases where Elastic starts logging deprecation warnings and errors for unused features. For example we see alerts about certificate common name usage which will be deprecated, but we have no certificates which have no common name. Imho they should only log deprecation warnings when something that is actually used gets deprecated.. But for some reason they choose to also log some of these deprecation warnings for no obvious reason other then waste our time wth is going on.

Willem