[IGNITE-23340] .NET: Some BigDecimal values can't be represented

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: .NET, platforms
• Labels: ignite-3 important
• Release Note: .NET: Added BigDecimal type to support full range of values that Ignite can handle.
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 02/Oct/24 12:05
• Updated: 25/Oct/24 09:44
• Resolved: 16/Oct/24 12:53

Description

• BigDecimal in Ignite 3 (in Java) can have precision up to 32767 (see MAX_DECIMAL_PRECISION)
• .NET decimal has 28-29 digit precision

As a result, some values can't be represented at all (e.g. SQL query results, Java compute job results, etc), leaving the user in a dead end.

To solve this, we should introduce a custom type (IgniteDecimal or something like that), which will consist of unscaled BigInteger and int scale, with a conversion to and from decimal.

Issue Links

• blocks: IGNITE-23243 .NET: LINQ: Value was either too large or too small for a Decimal
• links to: GitHub Pull Request #4573
• links to: IGNITE-23340 .NET: Add BigDecimal type by ptupitsyn · Pull Request #4573 · apache/ignite-3