Deprecated API
Contents
-
Deprecated InterfacesInterfaceDescriptionSee
ResolvedSchemaandConstraint.Please useAsyncLookupFunctionProviderto implement asynchronous lookup table.Please useLookupFunctionProviderto implement synchronous lookup table.Descriptorwas primarily used for the legacy connector stack and have been deprecated. UseTableDescriptorfor creating sources and sinks from the Table API.This interface has been replaced byFactory.This interface has been replaced byDynamicTableSinkFactory. The new interface consumes internal data structures. See FLIP-95 for more information.This interface has been replaced byDynamicTableSourceFactory. The new interface produces internal data structures. See FLIP-95 for more information.This interface will not be supported in the new sink design aroundDynamicTableSink. UseSupportsOverwriteinstead. See FLIP-95 for more information.This interface will not be supported in the new sink design aroundDynamicTableSink. UseSupportsPartitioninginstead. See FLIP-95 for more information.This interface has been replaced byDynamicTableSink. The new interface consumes internal data structures. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. Use the concept of computed columns instead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. Use the concept of computed columns instead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. Use the concept of computed columns instead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. UseSupportsFilterPushDowninstead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. UseSupportsLimitPushDowninstead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. UseLookupTableSourceinstead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. UseSupportsProjectionPushDowninstead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. UseSupportsPartitionPushDowninstead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. UseSupportsProjectionPushDowninstead. See FLIP-95 for more information.This interface has been replaced byDynamicTableSource. The new interface produces internal data structures. See FLIP-95 for more information.
-
Deprecated ClassesClassDescriptionThis utility will be dropped soon.
DynamicTableFactoryis based onConfigOptionand catalogs useCatalogPropertiesUtil.The legacy CSV connector has been replaced byFileSource/FileSink. It is kept only to support tests for the legacy connector stack.Non-legacy functions can simply omit this wrapper for declarations.Non-legacy functions can simply omit this wrapper for declarations.Non-legacy functions can simply omit this wrapper for declarations.Non-legacy functions can simply omit this wrapper for declarations.SeeResolvedSchemaandUniqueConstraint.SeeResolvedSchemaandColumn.This class has been deprecated as part of FLIP-164. It has been replaced by two more dedicated classesSchemaandResolvedSchema. UseSchemafor declaration in APIs.ResolvedSchemais offered by the framework after resolution and validation.This class will be removed in future versions as it uses the old type system. It is recommended to useDataTypesinstead which uses the new type system based on instances ofDataType. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.SeeResolvedSchemaandWatermarkSpec.This class was used for legacy connectors usingDescriptor.This class was used for legacy connectors usingDescriptor.This interface will not be supported in the new source design aroundDynamicTableSource. Use the concept of computed columns instead. See FLIP-95 for more information.This interface will not be supported in the new source design aroundDynamicTableSource. Use the concept of computed columns instead. See FLIP-95 for more information.UseRawTypeinstead.This utility is based onTypeInformation. However, the Table & SQL API is currently updated to useDataTypes based onLogicalTypes. UseLogicalTypeParserinstead.This class is implementing the deprecatedTableSinkinterface. ImplementDynamicTableSinkdirectly instead.UseDataTypeFactory.createDataType(TypeInformation)instead. Note that this method will not create legacy types anymore. It fully uses the new type system available only in the planner.This class will be removed in future versions as it is used for the old type system. It is recommended to useDataTypesinstead. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.This class will be removed in future versions as it is used for the old type system. It is recommended to useDataTypesinstead. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.
-
Deprecated ExceptionsExceptionsDescriptionThis exception is considered internal and has been erroneously placed in the *.api package. It is replaced by
AmbiguousTableFactoryExceptionand should not be used directly anymore.This exception is considered internal and has been erroneously placed in the *.api package. It is replaced byExpressionParserExceptionand should not be used directly anymore.This exception is considered internal and has been erroneously placed in the *.api package. It is replaced byNoMatchingTableFactoryExceptionand should not be used directly anymore.
-
Deprecated FieldsFieldDescriptionThis is only required for the legacy factory stack
-
Deprecated MethodsMethodDescriptionUse
FunctionHint.arguments()instead.UseFunctionHint.arguments()instead.UseProcedureHint.arguments()instead.UseProcedureHint.arguments()instead.This method returns the deprecatedTableSchemaclass. The old class was a hybrid of resolved and unresolved schema information. It has been replaced by the newSchemawhich is always unresolved and will be resolved by the framework later.This method returns the deprecatedTableSchemaclass. The old class was a hybrid of resolved and unresolved schema information. It has been replaced by the newResolvedSchemawhich is resolved by the framework and accessible viaResolvedCatalogBaseTable.getResolvedSchema().This method uses the old type system and is based on the old reflective extraction logic. The method will be removed in future versions and is only called when using the deprecatedTableEnvironment.registerFunction(...)method. The new reflective extraction logic (possibly enriched withDataTypeHintandFunctionHint) should be powerful enough to cover most use cases. For advanced users, it is possible to overrideUserDefinedFunction.getTypeInference(DataTypeFactory).This method uses the old type system and is based on the old reflective extraction logic. The method will be removed in future versions and is only called when using the deprecatedTableEnvironment.registerFunction(...)method. The new reflective extraction logic (possibly enriched withDataTypeHintandFunctionHint) should be powerful enough to cover most use cases. For advanced users, it is possible to overrideUserDefinedFunction.getTypeInference(DataTypeFactory).This method uses the old type system and is based on the old reflective extraction logic. The method will be removed in future versions and is only called when using the deprecatedTableEnvironment.registerFunction(...)method. The new reflective extraction logic (possibly enriched withDataTypeHintandFunctionHint) should be powerful enough to cover most use cases. For advanced users, it is possible to overrideUserDefinedFunction.getTypeInference(DataTypeFactory).This method uses the old type system and is based on the old reflective extraction logic. The method will be removed in future versions and is only called when using the deprecatedTableEnvironment.registerFunction(...)method. The new reflective extraction logic (possibly enriched withDataTypeHintandFunctionHint) should be powerful enough to cover most use cases. For advanced users, it is possible to overrideUserDefinedFunction.getTypeInference(DataTypeFactory).This method uses the old type system and is based on the old reflective extraction logic. The method will be removed in future versions and is only called when using the deprecatedTableEnvironment.registerFunction(...)method. The new reflective extraction logic (possibly enriched withDataTypeHintandFunctionHint) should be powerful enough to cover most use cases. For advanced users, it is possible to overrideUserDefinedFunction.getTypeInference(DataTypeFactory).This method uses the old type system and is based on the old reflective extraction logic. The method will be removed in future versions and is only called when using the deprecatedTableEnvironment.registerFunction(...)method. The new reflective extraction logic (possibly enriched withDataTypeHintandFunctionHint) should be powerful enough to cover most use cases. For advanced users, it is possible to overrideUserDefinedFunction.getTypeInference(DataTypeFactory).UseTableColumn.physical(String, DataType)instead.UseTableColumn.computed(String, DataType, String)instead.This method will be removed in future versions as it uses the old type system. It is recommended to useTableSchema.Builder.field(String, DataType)instead which uses the new type system based onDataTypes. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.This method will be removed soon. UseDataTypesto declare types.This method will be removed in future versions as it uses the old type system. It is recommended to useTableSchema.getFieldDataType(int)instead which uses the new type system based onDataTypes. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.This method will be removed in future versions as it uses the old type system. It is recommended to useTableSchema.getFieldDataType(String)instead which uses the new type system based onDataTypes. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.This method will be removed in future versions as it uses the old type system. It is recommended to useTableSchema.getFieldDataTypes()instead which uses the new type system based onDataTypes. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.UseTableSchema.toRowDataType()instead.This method will be removed in future versions as it uses the old type system. Please useSchema.field(String, DataType)instead.TableSinkFactory.Contextcontains more information, and already contains table schema too. Please useTableSinkFactory.createTableSink(Context)instead.TableSinkFactory.Contextcontains more information, and already contains table schema too. Please useTableSinkFactory.createTableSink(Context)instead.TableSourceFactory.Contextcontains more information, and already contains table schema too. Please useTableSourceFactory.createTableSource(Context)instead.TableSourceFactory.Contextcontains more information, and already contains table schema too. Please useTableSourceFactory.createTableSource(Context)instead.This method will be dropped in future versions. It is recommended to pass a static schema when instantiating the sink instead.Use the field names ofTableSink.getTableSchema()instead.Use the field types ofTableSink.getTableSchema()instead.This method will be removed in future versions as it uses the old type system. It is recommended to useTableSink.getConsumedDataType()instead which uses the new type system based onDataTypes. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.This method will be removed in future versions as it uses the old type system. It is recommended to useTableSource.getProducedDataType()instead which uses the new type system based onDataTypes. Please make sure to use either the old or the new type system consistently to avoid unintended behavior. See the website documentation for more information.Table schema is a logical description of a table and should not be part of the physical TableSource. Define schema when registering a Table either in DDL or inTableEnvironment#connect(...).UseTypeInference.Builder.staticArguments(List)instead.UseTypeInference.Builder.staticArguments(List)instead.UseTypeInference.Builder.staticArguments(List)instead.UseTypeInference.getStateTypeStrategies()instead.UseTypeInference.getStaticArguments()instead.UseTypeInference.getStaticArguments()instead.UseTypeInference.getStaticArguments()instead.Use theProjectiontypeUse theProjectiontypePlease don't use this method anymore. It will be removed soon and we should not make the removal more painful. Sources and sinks should use the method available in context to convert, within the planner you should use eitherInternalTypeInfoorExternalTypeInfodepending on the use case.Please don't use this method anymore. It will be removed soon and we should not make the removal more painful. Sources and sinks should use the method available in context to convert, within the planner you should use eitherInternalTypeInfoorExternalTypeInfodepending on the use case.Please don't use this method anymore. It will be removed soon and we should not make the removal more painful. Sources and sinks should use the method available in context to convert, within the planner you should use eitherInternalTypeInfoorExternalTypeInfodepending on the use case.Please don't use this method anymore. It will be removed soon and we should not make the removal more painful. Sources and sinks should use the method available in context to convert, within the planner you should use eitherInternalTypeInfoorExternalTypeInfodepending on the use case.UseEncodingUtils.loadClass(String, ClassLoader)instead, in order to explicitly provide the correct classloader.
-
Deprecated Constructors
-
Deprecated Annotation Type ElementsAnnotation Type ElementDescriptionUse
FunctionHint.arguments()instead.UseFunctionHint.arguments()instead.UseProcedureHint.arguments()instead.UseProcedureHint.arguments()instead.
Descriptorfor details.