Table of documentation contents

Deprecation messages

Deprecation messages intro

The list below contains deprecation messages:

rest-meta-prop

use of deprecated property ?meta=true/false

statusdeprecated
API typeREST
locationGET /v1/thing/{id}
locationGET /v1/things
locationGET /v1/action/{id}
locationGET /v1/actions
mitigationUse ?include=<propName>, e.g. ?include=_classification for classification meta or ?include=_vector to show the vector position or ?include=_classification,_vector for both. When consuming the response use the underscore fields such as _vector, as the meta object in the reponse, such as meta.vector will be removed.
since version0.22.8
since timeMon, 15 Jun 2020 16:18:06 +0000
planned removal version0.23.0
removed in version
removed in date

config-files

use of deprecated command line argument –config-file

statusdeprecated
API typeConfiguration
location--config-file=""
mitigationConfigure Weaviate using environment variables.
since version0.22.16
since timeTue, 08 Sep 2020 09:46:00 +0000
planned removal version0.23.0
removed in version
removed in date

cardinality

use of deprecated property option ‘cardinality’

statusdeprecated
API typeREST
locationGET /v1/schema
locationPOST /v1/schema/things
locationPOST /v1/schema/actions
locationPOST /v1/schema/things/{className}/properties
locationPOST /v1/schema/actions/{className}/properties
mitigationOmit this field. Starting in 0.22.7 it no longer has any effect.
since version0.22.17
since timeWed, 16 Sep 2020 09:06:00 +0000
planned removal version0.23.0
removed in version
removed in date

Tags
  • Deprecation messages