Skip to content

Conversation

@AMashenkov
Copy link
Member

Add missed types in tests.
# Conflicts:
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/KVMarshaller.java
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/MarshallerUtil.java
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/asm/AsmSerializerGenerator.java
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/reflection/FieldAccessor.java
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/reflection/JavaSerializer.java
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/reflection/Marshaller.java
#	modules/schema/src/test/java/org/apache/ignite/internal/schema/marshaller/JavaSerializerTest.java
#	modules/schema/src/test/java/org/apache/ignite/internal/schema/marshaller/reflection/FieldAccessorTest.java
#	modules/schema/src/test/java/org/apache/ignite/internal/schema/registry/UpgradingRowAdapterTest.java
#	modules/table/src/main/java/org/apache/ignite/internal/schema/marshaller/KVMarshaller.java
#	modules/table/src/main/java/org/apache/ignite/internal/schema/marshaller/KvMarshaller.java
#	modules/table/src/main/java/org/apache/ignite/internal/table/KeyValueViewImpl.java
#	modules/table/src/test/java/org/apache/ignite/internal/table/KeyValueViewOperationsSimpleSchemaTest.java
# Conflicts:
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/asm/ColumnAccessCodeGenerator.java
#	modules/schema/src/main/java/org/apache/ignite/internal/schema/marshaller/reflection/Marshaller.java
#	modules/schema/src/test/java/org/apache/ignite/internal/schema/marshaller/JavaSerializerTest.java
#	modules/schema/src/test/java/org/apache/ignite/internal/schema/marshaller/reflection/FieldAccessorTest.java
* @param val Object to map to native type.
* @return {@code null} for {@code null} value. Otherwise returns NativeType according to the value's type.
*/
@Contract("null -> null")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What reason to add jetbrains annotations? I think we should start discussion at least internally before starting it.

Copy link
Member Author

@AMashenkov AMashenkov Nov 11, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already use jetbrains annotations in the project (see @Nullable and @NotNull).
The contract is clearly described in javadoc and the annotation just helps to suppress IDEA warning and affect nothing.

Proof:
Note that this annotation just describes how the code works and doesn't add any functionality by means of code generation.

@AMashenkov AMashenkov merged commit ba18299 into apache:main Nov 12, 2021
@AMashenkov AMashenkov deleted the ignite-15783 branch November 12, 2021 09:59
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

Successfully merging this pull request may close these issues.

2 participants