Looks like that bug report refers to the same version I encountered it on (11.29.3 Mar2018), and it's essentially the same bug, so I think there's no need to report it again. I'll try it when the next release is out.
Thanks for your help!
Marcell
-----Original Message----- From: users-list [mailto:users-list-bounces+marcell.bernat=arh.hu@monetdb.org] On Behalf Of Sjoerd Mullender Sent: Thursday, May 10, 2018 9:40 AM To: users-list@monetdb.org Subject: Re: Problem/bug with remote tables
I tried it, and I could reproduce the problem, so even if it's the same bug, it wasn't fixed.
On 2018-05-10 08:30, Joeri van Ruth wrote:
I think this has already been fixed as bug https://www.monetdb.org/bugzilla/show_bug.cgi?id=6584
Joeri
On 9 May 2018 at 15:10:59, Sjoerd Mullender (sjoerd@acm.org mailto:sjoerd@acm.org) wrote:
Indeed. Looks like a bug. Can you report it on bugs.monetdb.org, please?
On 09/05/18 13:29, Bernát Marcell wrote:
Hello everyone,
I believe I’ve encountered a bug with the remote table functionality. Here are the steps to replicate it. Tested with MonetDB 11.29.3, both on Ubuntu 14.04.5 LTS and Ubuntu 16.04.4 LTS. The problem persists even after restarting the DB farms and the MonetDB daemons.
_On node 1_
Create a normal table, insert some data and check its contents:
create table testtable(id int not null, name text, valid boolean);
insert into testtable (id, name) values (1, '1');
insert into testtable (id, name) values (2, '2');
insert into testtable (id) values (3);
select * from testtable;
+------+------+-------+
| id | name | valid |
+======+======+=======+
| 1 | 1 | null |
| 2 | 2 | null |
| 3 | null | null |
+------+------+-------+
3 tuples (6.446ms)
_On node 2_
Create a remote table and check its contents to make sure it works:
create remote table testtable(id int not null, name text, valid boolean) on 'mapi:monetdb://node1:50000/dbfarm';
select * from testtable;
+------+------+-------+
| id | name | valid |
+======+======+=======+
| 1 | 1 | null |
| 2 | 2 | null |
| 3 | null | null |
+------+------+-------+
3 tuples (6.446ms)
Then try to select anything with a WHERE clause:
select * from testtable where name is null;
+------+------+-------+
| id | name | valid |
+======+======+=======+
| 3 | null | null |
+------+------+-------+
1 tuple (5.186ms)
It *seemingly* works fine, but now when you try to select anything else, you get the same result:
select * from testtable;
+------+------+-------+
| id | name | valid |
+======+======+=======+
| 3 | null | null |
+------+------+-------+
1 tuple (4.466ms)
If you log out from mclient and then back in, select * works fine again, so there’s no data loss. However, even if you try the opposite of the previous query (is not null instead of is null), you get the same result:
select * from testtable where name is not null;
+------+------+-------+
| id | name | valid |
+======+======+=======+
| 3 | null | null |
+------+------+-------+
1 tuple (5.358ms)
Can someone else please try this to confirm it’s a bug and not something on my end?
Thanks in advance.
Best regards,
Marcell
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- Sjoerd Mullender
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- Sjoerd Mullender