Martin,
I just merged recent changes from Feb2013 into default,
and while doing so resolved --- hopefully correctly; see below ---
some conflicts that occurred in opt_evaluate.c & mal_dataflow.c .
In fact,
(1)
I first merged up until before your changeset that
introduced the new multiple worker pools, cf.,
http://dev.monetdb.org/hg/MonetDB/rev/10125a9c3976
(2)
then merged only that very changeset, cf.,
http://dev.monetdb.org/hg/MonetDB/rev/1eea7fa4cc7c
(3)
and finally merge the rest, cf.,
http://dev.monetdb.org/hg/MonetDB/rev/3e3d7d5f8dc9
During (1), I resolved some conflicts in opt_evaluate.c due to
http://dev.monetdb.org/hg/MonetDB/rev/62ed11377998
I hope, I did this correctly.
However, there are still some differences in opt_evaluate.c
between Feb2013 & default; cf.,
hg diff -p -r Feb2013 -r default monetdb5/optimizer/opt_evaluate.c
Could you please check, whether these are OK?
During (2), I resolved some conflicts in mal_dataflow.c due to
http://dev.monetdb.org/hg/MonetDB/rev/4c47797192f4
I hope, I did this correctly.
However, there are still some differences in mal_dataflow.c
between Feb2013 & default; cf.,
hg diff -p -r Feb2013 -r default monetdb5/mal/mal_dataflow.c
Could you please check, whether these are OK?
It appears, that after (2), some tests in sql/jdbc/tests/Tests/
run into a timeout (only when run multi-threaded, i.e., not when
run single-threaded) --- I have not yet been able to find out why ...
Thanks!
Stefan
--
| Stefan.Manegold(a)CWI.nl | DB Architectures (DA) |
| www.CWI.nl/~manegold/ | Science Park 123 (L321) |
| +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |
Hello All,
I am new to MonetDB and would like to profile the MonetDB kernel to find out the functions that are most frequently executed while it runs TPCH. So far, I have tried compiling with "--enable-profile" but it seems that gmon.out files are not generated. Is there a recommend way of doing function level profiling in MonetDB?
Thanks,
Geoffrey
Hoi Jennie,
> Changeset: 58e31783ae0f for MonetDB
> URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=58e31783ae0f
> Modified Files:
> monetdb5/modules/mal/array.mx
> sql/server/rel_dump.c
> sql/server/rel_exp.c
> sql/server/rel_select.c
> sql/test/sciql/Tests/teleios_noa_bsm.sql
> Branch: SciQL-2
> Log Message:
>
> handle non-rectangular array tiles
>
> - accept either interval tile range, or point tile ragnes, no mix of them
> - multiple tile ranges are appended to e_column->f, thus e_column->f list can
> have more than 3 items.
> - to distinguish a point range from an interval range: a point range only has
> one expr., while an interval range has three
Thanks!
> array.mx:
> - save the values for the error message, since the lists are freed in
> AGGR_CLEANUP
Nice catch ;-) --- Thanks for fixing! ... and sorry for overlooking it myself ;-)
> - disable the check on (max - min + 1 = size), since it only holds for
> stepsize = 1.
> maybe we should just remove this check, since we don't have step size in
> the
> tiling aggr impl. functions, do we?
IMHO, our current tiled aggregation implementation inherently assumes (and thus requires) that all dimensions of the given array have step-size == 1. Since ARRAYtiles*() does not get the step sizes of the given array as parameters, the check (max - min + 1 = size) was/is IMHO the only way to check/ensure that we are indeed working on an array where all dimensions have step-size == 1.
> teleios_noa_bsm.sql:
> now we can get rid of the workarounds
>
> more tests needed...
Indeed --- I'll resume me test tonight or tomorrow ...
Best,
Stefan
--
| Stefan.Manegold(a)CWI.nl | DB Architectures (DA) |
| www.CWI.nl/~manegold/ | Science Park 123 (L321) |
| +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |
Hi,
Is there any plan to support UTF-8 charactors for column names (or
object identifiers) in MonetDB? I think it's not supported so far.
Right?
I'm trying to port my database from a row-store one to MonetDB.
Now, we are using UTF-8 charactors (Japanese) in column names,
so we need to convert them manually.
Obviously, it is possible, but if MonetDB can support UTF-8 charactors
in column name, it would be easier to get porting our database to
MonetDB.
And I found the related thread and feature request on this.
[MonetDB-users] 答复: Does Monetdb supports UTF-8 characters when I use
'as' clause?
http://mail.monetdb.org/pipermail/users-list/2012-February/005397.html
Bug 3010 - Does not currently support non-ASCII names in identifiers
http://bugs.monetdb.org/show_bug.cgi?id=3010#c2
Is there any particluar plan? Is it difficult to implement?
Regards,
--
Satoshi Nagayasu <snaga(a)uptime.jp>
Uptime Technologies, LLC. http://www.uptime.jp
In sort, there is a slight problem with a server side check to prevent users from pushing in unresolved merge conflicts.
The problem materializes such that one can checkin such conflicts, but then not (easily) remove them, again.
Having you .hgrc up to date as "requested", in particular the whitespace hook
[hooks]
pretxncommit.whitespace = python:<path-to-check_whitespace-directory>/check_whitespace.py:hook
prevent the checkin of unresolved unresolved merge conflicts (already) on the client side.
(We'll fully fix the server side once Sjoerd is back from vacation.)
Stefan
----- Original Message -----
> Hi stefan,
>
> can you please share some more information about the problem? how can
> configurations of local files on the client side affect the server/main
> repository? I am asking for purely academic reasons. Is there some kind of
> security problem in hg?
>
> ----- Original Message -----
> > Dear all,
> >
> > the MonetDB Mercurial (HG) repository should be working, again.
> >
> > IMPORTANT NOTE:
> >
> > To prevent further problems, it is mandatory that you do consciously read
> > http://www.monetdb.org/Assets/MonetDB-Mercurial.html
> > and follow all instructions carefully.
> >
> > In particular, your .hgrc must contain all of the "Important Configuration"
> > mention in above document.
> >
> > You must double-check your .hgrc before your next hg pull, hg commit or hg
> > push,
> > which ever comes first.
> >
> > Thanks!
> > Stefan
> >
> > ----- Original Message -----
> > > Dear all,
> > >
> > > there seems to be a problem with the MonetDB HG (Mercurial) repository.
> > > Please refrain from pushing to it until we have sorted-out the problem.
> > >
> > > Thanks!
> > > Stefan
> >
> > --
> > | Stefan.Manegold(a)CWI.nl | DB Architectures (DA) |
> > | www.CWI.nl/~manegold/ | Science Park 123 (L321) |
> > | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |
> >
> >
>
--
| Stefan.Manegold(a)CWI.nl | DB Architectures (DA) |
| www.CWI.nl/~manegold/ | Science Park 123 (L321) |
| +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |
Dear all,
there seems to be a problem with the MonetDB HG (Mercurial) repository.
Please refrain from pushing to it until we have sorted-out the problem.
Thanks!
Stefan
--
| Stefan.Manegold(a)CWI.nl | DB Architectures (DA) |
| www.CWI.nl/~manegold/ | Science Park 123 (L321) |
| +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |