Limit of 32 attributes per element
Monday, 13 December 2010 · 5 messages · last reply 15 Dec 2010
PF
Peter Fischer13 Dec 2010 11:50 #
Dear all,
when testing BaseX with the TPoX benchmark workload
(http://tpox.sourceforge.net/) I could not load the input data set since it contains elements with more than 32 attributes.
The large number of attributes stems from the FIXML data
(http://www.fixprotocol.org/specifications/fix4.4fixml) contained in the workload, so it is not just a stress test by the benchmark designers.
Is there any way to lift this limitation?
Best Regards,
Peter
--
Dr. Peter Fischer Systems Group/D-INFK/ETH Zurich peter.fischer at inf.ethz.ch Tel: +41/44/632 36 16 http://www.systems.ethz.ch/people/petfisch Universitätstr 6, CAB E75
AW
Andreas Weiler13 Dec 2010 13:11 #
Hi Peter,
currently the number of attributes for an element is limited to 32. Maybe we will increase the number of attributes for an element in a future release.
Kind regards,
Andreas
Quoted text · Peter Fischer · 15 lines
Am 13.12.10 11:50, schrieb Peter Fischer: > Dear all, > > when testing BaseX with the TPoX benchmark workload > (http://tpox.sourceforge.net/) I could not load the input data set since > it contains elements with more than 32 attributes. > > The large number of attributes stems from the FIXML data > (http://www.fixprotocol.org/specifications/fix4.4fixml) contained in the > workload, so it is not just a stress test by the benchmark designers. > > Is there any way to lift this limitation? > > Best Regards, > Peter
CG
Hi Peter,
thanks for your hints. I've found a simple solution to increase the maximum number of attributes per element to 2^31, which should hopefully be enough (well, who knows?..). Please have a look at the latest stable version 6.3.4 (http://basex.org/download).
Feedback on your experiences with BaseX and the TPoX Benchmark is welcome! Christian
_____________________________
2010/12/13 Peter Fischer <peter.fischer at inf.ethz.ch>:
Quoted text · Peter Fischer · 18 lines
> Dear all, > > when testing BaseX with the TPoX benchmark workload > (http://tpox.sourceforge.net/) I could not load the input data set since > it contains elements with more than 32 attributes. > > The large number of attributes stems from the FIXML data > (http://www.fixprotocol.org/specifications/fix4.4fixml) contained in the > workload, so it is not just a stress test by the benchmark designers. > > Is there any way to lift this limitation? > > Best Regards, > Peter > -- > Dr. Peter Fischer Systems Group/D-INFK/ETH Zurich > peter.fischer at inf.ethz.ch Tel: +41/44/632 36 16 > http://www.systems.ethz.ch/people/petfisch Universitätstr 6, CAB E75
PF
Peter Fischer15 Dec 2010 17:55 #
Quoted text · Christian Grün · 2 lines
On 12/14/2010 02:57 AM, Christian Grün wrote: > Hi Peter,
Hi Christian,
all,
Quoted text · Christian Grün · 4 lines
> thanks for your hints. I've found a simple solution to increase the > maximum number of attributes per element to 2^31, which should > hopefully be enough (well, who knows?..). Please have a look at the > latest stable version 6.3.4 (http://basex.org/download).
thanks for the quick fix. I can confirm that now the TPoX workload can be executed by BaseX 6.3.4.
It seems that the only remaining problem was the change in the order of parameters to the CREATE DB command. With versions 6.0 and 6.1 the document came before the database, now it is the other way. I could not find any explicit information in the documentation, so this might be something to point out in the change logs.
Quoted text · Christian Grün · 1 line
> Feedback on your experiences with BaseX and the TPoX Benchmark is welcome!
Regards,
Peter
Quoted text · Christian Grün · 22 lines
> Christian > _____________________________ > > 2010/12/13 Peter Fischer <peter.fischer at inf.ethz.ch>: >> Dear all, >> >> when testing BaseX with the TPoX benchmark workload >> (http://tpox.sourceforge.net/) I could not load the input data set since >> it contains elements with more than 32 attributes. >> >> The large number of attributes stems from the FIXML data >> (http://www.fixprotocol.org/specifications/fix4.4fixml) contained in the >> workload, so it is not just a stress test by the benchmark designers. >> >> Is there any way to lift this limitation? >> >> Best Regards, >> Peter >> -- >> Dr. Peter Fischer Systems Group/D-INFK/ETH Zurich >> peter.fischer at inf.ethz.ch Tel: +41/44/632 36 16 >> http://www.systems.ethz.ch/people/petfisch Universitätstr 6, CAB E75
--
Dr. Peter Fischer Systems Group/D-INFK/ETH Zurich peter.fischer at inf.ethz.ch Tel: +41/44/632 36 16 http://www.systems.ethz.ch/people/petfisch Universitätstr 6, CAB E75
CG
Christian Grün15 Dec 2010 20:50 #
Quoted text · Peter Fischer · 5 lines
> It seems that the only remaining problem was the change in the order of > parameters to the CREATE DB command. With versions 6.0 and 6.1 the > document came before the database, now it is the other way. I could not > find any explicit information in the documentation, so this might be > something to point out in the change logs.
...true; this change has only been documented in our subversion comments. The new syntax will remain stable for future versions, as well as other changes on the commands that have been performed after Version 6.0.
Christian
Written for BaseX 6. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery