Hello!
thanks for prompt resolution, will try once 2.8 is out.
Best!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
No, I am not using JDBC driver.
Re switching to the pessimistic transaction, tried but is not working
correctly in some cases, for instance, .clear() on caches and some more...
which is fine as Igniters state it's not production ready yet. Obviously
happy guys you are adding new transaction
Hello!
Cross-posting: I have filed a blocker ticket about it.
https://issues.apache.org/jira/browse/IGNITE-10884
Regards,
--
Ilya Kasnacheev
чт, 3 янв. 2019 г. в 03:24, Denis Magda :
> Are you using JDBC/ODBC drivers? Just want to know why it's hard to
> execute SQL queries outside of
Are you using JDBC/ODBC drivers? Just want to know why it's hard to execute
SQL queries outside of transactions.
Can you switch to pessimistic transactions instead?
--
Denis
On Wed, Jan 2, 2019 at 7:24 AM whiteman wrote:
> Hi guys,
>
> As far as I am concerned this is a breaking behaviour. In
Hi guys,
As far as I am concerned this is a breaking behaviour. In Apache Ignite v
2.5 it was possible to have the SQL query inside the optimistic serializable
transaction. Point here is that SQL query might not be part of the
transaction (no guarantees) but was at least performed. In 2.7 this
Thanks.
This helped, but it requires deactivate all cluster and delete "work" dir,
else i had error like "different field type parentId: field1: Object,
field2: uuid". Just restart cluster didn't help. I found one way: recreate
uuid field via sql (sqline) without data lost (create other column,
Hello!
Looks like you can't have a generic field in your class and then put UUID
to it.
UUID is a primitive type as far as Ignite is concerned, which will take 6
bytes, but a smallest Object (which is the fallback type for generic field)
is 8 bytes, hence cryptic errors.
If you change P to UUID
Thanks. I use sql in transaction context, but in 2.6 I havent problem this.
Now I changed mode to TRANSACTIONAL_SNAPSHOT and Transaction to pessimistic
repeatable and problem was gone.
About first problem.. I create small project to reproduce it.
Hi Andrey,
It looks like you try to run "Select" sql query inside explicit transaction.
Please, let us know if it is not true.
This was workable in 2.7 as SQL had no transactional support and query just
ignored transactional context (however "Select for Update" wasn't).
For now, SQL Select query
Hi Andrey,
It looks like your persisted data was read incorrectly by upgraded
Ignite. It would be great if you provide runnable reproducer.
Regarding Optimistic Serializable transactions. They are still
supported by caches with TRANSACTIONAL atomicity mode. In your error
it looks like that your
Hello, when I tried to migrate to new version i had error. Optimistic
Serializable isn't supported?
```
Caused by: class
org.apache.ignite.internal.processors.query.IgniteSQLException: Only
pessimistic repeatable read transactions are supported at the moment.
at
11 matches
Mail list logo
