tarantool / document Goto Github PK

Will field updates be supported?

Step to reproduce:

1. Create space and insert documents as in sample
   tarantool> box.schema.create_space('TEST_DOC', {if_not_exists = true})
   tarantool> doc.create_index(box.space.TEST_DOC, 'primary',{parts={'id', 'unsigned'}, if_not_exists=true})
   tarantool> doc.insert(box.space.TEST_DOC, {id=1, foo="foo", bar={baz=3}})

2. Verify that data is inserted
   tarantool> for _, r in doc.select(box.space.TEST_DOC) do
   print('tuple:', json.encode(r))
   end

tuple:  {"bar":{"baz":3},"foo":"foo","id":1}
---
...

3. Select data with SQL interface
   tarantool> box.sql.execute([[select * from TEST_DOC]]);

Expected: tuples with documents.

Actual: SQL error

- error: 'no such table: TEST_DOC'
...

Additional data:
tarantool> box.sql.execute([[SELECT * FROM _space;]])

  - [528, 1, 'TEST_DOC', 'memtx', 0, !!binary gA==, !!binary k4OkdHlwZah1bnNpZ25lZKRuYW1lomlkq2lzX251bGxhYmxlwoOkdHlwZaZzY2FsYXKkbmFtZadiYXIuYmF6q2lzX251bGxhYmxlw4OkdHlwZaZzdHJpbmekbmFtZaNmb2+raXNfbnVsbGFibGXD]

tarantool> box.info.version

---
- 1.8.3-77-ge5b5dbc
...

Hi, I've found out that tarantool crashes when I insert a tuple with a different format.

-- Tarantool: 1.9.0-52-g38b2a29ff

local profileSpace = box.schema.create_space('profile', {
    engine = 'vinyl'
})

local doc = require("document")

doc.create_index(profileSpace, 'primary', {parts={'oid', 'string'}})
doc.insert(profileSpace, {oid = 'test1'})
doc.insert(profileSpace, {oid = 'test2', email = 'test2@mail'})

Error: Vinyl does not support changing space format of a non-empty space

It would be cool to have a RPM and Debian packages, like a tarantool-avro-schema or tarantool-http

When I want to build a RPM package for my application, I specify in the rpm.spec:

Requires: tarantool >= x.y.z
Requires: tarantool-module-required >= x.y.z

but using the tarantool-document I can't do this, I need to copy document.lua to my source code every time, if I want to update application's dependencies

tarantool/tarantool#7904 exports schema version to public API and Lua:
start using it, when available, instead of unreliable internal API.