Releases: ydb-platform/yoj-project
Releases · ydb-platform/yoj-project
YOJ 2.2.5-3
More backports of fixes to 2.2.5
YOJ 2.2.11 (bugfix release)
- #58:
yoj-ydb-repository-v2
: Defer initialization of YDB GRPC Transport fromYdbRepository
constructor to first use, to make v2 work more like v1 - #63:
yoj-ext-meta-generator
: Fix annotation processor self-registration to make it usable with Gradle - FIX: Disallow relative paths in
YdbConfig.tablespace
andYdbConfig.database
, they were never supported, anyway (a7123cf)
YOJ 2.2.5-2 (2.2.5 + annotation processor)
Release of YOJ 2.2.5 (last 2.2.x version with no Custom Value Types) but with add-ons:
- 🎁 Add-on: Annotation processor for field name constant generation,
yoj-ext-meta-generator
(#57):
https://github.com/ydb-platform/yoj-project/tree/main/ext-meta-generator
YOJ 2.2.10 (annotation processor, custom conversion improvements)
- 🎁 Add-on: Annotation processor for field name constant generation,
yoj-ext-meta-generator
(#57):
https://github.com/ydb-platform/yoj-project/tree/main/ext-meta-generator - Custom Value Type improvements
- Cache custom value type annotations and
ValueConverter
instances for eachSchema.JavaField
of a custom value type. This might improve performance of custom converter-heavy workloads. - Clean up
FieldValueType
and addlog.error()
for calls of@Deprecated(forRemoval)
methods⚠️ (potentially breaking)FieldValueType.forJavaType(Type, Column)
method has been removed in favor ofFieldValueType.forSchemaField(JavaField)
andFieldValueType.forJavaType(Type, ReflectField)
- Use new
StringValueConverter
logic to convert legacy string-value types registered byFieldValueType.registerStringValueType()
. In YOJ 2.2.x-2.4.x, legacy string-value types still work; they're removed in YOJ 2.5.0.⚠️ (potentially breaking)CommonConverters.{stringValueSetter,stringValueGetter,serializeStringValue,deserializeStringValue
methods have been permanently removed
- Improve custom converter documentation (
ValueConverter
,StringValueType
,StringColumn
etc.)
- Cache custom value type annotations and
- Meta-annotations: Add
@ObjectColumn
annotation to express@Column(flatten=false)
more clearly
YOJ 2.2.5-1 (2.2.5 + annotation processor)
yoj-ext-meta-generator
to the BOM artifact (yoj-bom
).
- 🎁 Add-on: Annotation processor for field name constant generation,
yoj-ext-meta-generator
(#57):
https://github.com/ydb-platform/yoj-project/tree/main/ext-meta-generator
YOJ 2.2.9 (aspect fix)
- #56: FIX: Add
javac
-parameters
flag so that Spring can detect method parameter names
YOJ 2.2.8 (aspect, fix perf issues)
ℹ️ This releases mostly fixes performance issues introduced with meta-annotation support in 2.2.6.
- Add
yoj-aspect
module which has a@YojTransactional
annotation for methods, and an AspectJ aspect implementing this annotation. This module can be used as-is with Spring AOP. - Exclude
java.*
annotations from meta-annotation scanning, mostly fixing perf issues brought by meta-annotation support (#54).
YOJ 2.2.7 (Fix for legacy string-valued types)
- FIX: Reestablish support for string-valued types registered by
FieldValueType.registerFieldValueType()
mostly using custom value types machinery (See 6de43ed)
YOJ 2.2.6 (meta-annotations)
- #50: Meta-annotation support for
@Column
and@CustomValueType
annotations: you can define annotations that define column mapping or type mapping.
E.g., a@StringColumn UUID myColumn
in an entity is equivalent to@Column(customValueType=@CustomValueType(columnClass=String.class, converter=StringValueConverter.class)) UUID myColumn
.
Same is possible for annotating types with predefined@CustomValueType
annotation, see e.g.@StringValueType
. - #51: Fix conversion errors for custom value types (#24 (comment))
YOJ v2.2.5 (minor bugfix)
#47: YdbSchemaCompatibilityChecker
bugfix on SCHEMA_ERROR