[
https://issues.apache.org/jira/browse/IGNITE-21844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-21844:
------------------------------------
Description:
IGNITE-19835 aimed to disallow any unmapped fields, but key-only operations
(such as *get*, *delete*, also in streamer) allow extra columns on the client
side.
Add this to *ItAbstractDataStreamerTest*:
{code:java}
@Test
public void test() {
RecordView<Tuple> view = defaultTable().recordView();
view.upsert(null, tuple(2, "_"));
view.get(null, tuple(2, "1234"));
}
{code}
The test fails in embedded mode and works in client mode.
was:
IGNITE-19835 aimed to disallow any unmapped fields, but key-only operations
(such as *get*, *delete*, also in streamer) allow extra columns on the client
side.
Add this to *ItAbstractDataStreamerTest*:
{code:java}
@Test
public void test() {
RecordView<Tuple> view = defaultTable().recordView();
view.upsert(null, tuple(2, "_"));
view.get(null, tuple(2, "1234"));
}
{code}
> Java thin 3.0: Key-only operations allow unmapped fields in tuples
> ------------------------------------------------------------------
>
> Key: IGNITE-21844
> URL: https://issues.apache.org/jira/browse/IGNITE-21844
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> IGNITE-19835 aimed to disallow any unmapped fields, but key-only operations
> (such as *get*, *delete*, also in streamer) allow extra columns on the client
> side.
> Add this to *ItAbstractDataStreamerTest*:
> {code:java}
> @Test
> public void test() {
> RecordView<Tuple> view = defaultTable().recordView();
> view.upsert(null, tuple(2, "_"));
> view.get(null, tuple(2, "1234"));
> }
> {code}
> The test fails in embedded mode and works in client mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
