Stanilovsky Evgeny created IGNITE-6501:
--
Summary: select distinct exception in simple sqlQuery request.
Key: IGNITE-6501
URL: https://issues.apache.org/jira/browse/IGNITE-6501
Project: Ignite
Yashasvi Kotamraju created IGNITE-6500:
--
Summary: While using ignite-cassandra-store, POJO field having
wrapper type, mapped to Cassandra table are getting initialized to respective
default value of primitive type instead of null if column v
Alexandr Kuramshin created IGNITE-6499:
--
Summary: Compact NULL fields binary representation
Key: IGNITE-6499
URL: https://issues.apache.org/jira/browse/IGNITE-6499
Project: Ignite
Issue
Vladimir,
I do not think we have a luxury of changing Ignite transaction APIs. It is
almost the same as changing Ignite put and get APIs. Too much code has
already been written to these APIs. The upgrade path will be so onerous
that no one will ever take it.
As far as the current transaction flag
Dima,
Becuase if you take any pair of our concurrency/isolation modes, you will
not find anything similar in SQL. The main problem is that there is no
"OPTIMISTIC" or "PESSIMISTIC" in SQL world. All reads are "optimistic", but
can be converted to "perssimistic" optionally, and all writes are
"pess
Pavel, we can optionally enforce that, but not by default.
Dmitry, the problem is the following. User configures Ignite cache and
query entity, does several puts than empty results for SQL. The reason is
very simple - typo in class name or simply different classes in
configuration and of actual ca
Vasiliy Sisko created IGNITE-6498:
-
Summary: Web console: Query metadata should show table alias when
configured
Key: IGNITE-6498
URL: https://issues.apache.org/jira/browse/IGNITE-6498
Project: Ignite
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/2744
IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache
enabled.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/i
Yakov,
Here are couple examples:
- http://apache-ignite-users.70518.x6.nabble.com/How-to-
correctly-shut-down-Ignite-Application-td12548.html
- http://apache-ignite-users.70518.x6.nabble.com/Nodes-
hanging-when-accessing-queue-td12343.html
*Andrey*, it seems that you give this kind of recommendat
Given that we already have a notion of CacheStore which comes from JCache
spec, I think having other stores may get confusing. I like
DurableMemoryConfiguration.
Other opinions?
D.
On Mon, Sep 25, 2017 at 12:24 PM, Vladimir Ozerov
wrote:
> Dima, let's finalize the design first.
>
> As I unders
Vladimir,
This looks like a complete overhaul of our transactional behavior and I do
not think we are at a liberty to make such drastic changes. Can you please
explain why the current behavior would not map to the SQL transactions?
D.
On Mon, Sep 25, 2017 at 12:09 PM, Vladimir Ozerov
wrote:
>
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/2425
---
Dima, let's finalize the design first.
As I understand, we are happy with idea to merge MemoryConfiguration
and PersistentStoreConfiguration
into something what I called DataConfiguration, and to rename
MemoryPolicyConfiguration to DataRegionConfiguration.
The only outstanding qurestion is whethe
Folks,
Sorry for late reply. I had a chat with several Ignite veterans today. We
tried to design transactional SQL for Ignite. One of our questions was how
to align SQL transactions with current Ignite transactions. And we failed.
And then we came to conclusion that current transaction API is unus
Yury Babak created IGNITE-6497:
--
Summary: Broken tests in ignite-2.1.5
Key: IGNITE-6497
URL: https://issues.apache.org/jira/browse/IGNITE-6497
Project: Ignite
Issue Type: Bug
Component
Vyacheslav Koptilin created IGNITE-6496:
---
Summary: Client node does not reconnect to server node when the
latter is restarted.
Key: IGNITE-6496
URL: https://issues.apache.org/jira/browse/IGNITE-6496
Hello, guys.
Currently, I’m working on integration between Spark and Ignite [1].
For now, I implement following:
* Ignite DataSource implementation(IgniteRelationProvider)
* DataFrame support for Ignite SQL table.
* IgniteCatalog implementation for a transparent resolving of ignites
S
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/2743
IGNITE-6445_txLocksInfo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-6445_txLocksInfo
Alternatively you can rev
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/2742
IGNITE-3084: Prototype of Ignite DataFrame support.
* DataSource and DataFrame implementation for Ignite SQL Tables.
* IgniteCatalog implementation.
* Some examples provided.
* There
Oleg Ignatenko created IGNITE-6495:
--
Summary: performance measurement of decision trees algorithms
Key: IGNITE-6495
URL: https://issues.apache.org/jira/browse/IGNITE-6495
Project: Ignite
Iss
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/2628
---
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/2663
---
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2741
IGNITE-6494 .NET: Fix CacheConfiguration.WriteSynchronizationMode default
value
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ig
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2740
IGNITE-6242
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6242
Alternatively you can review and apply th
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/2668
---
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/2641
---
Pavel Tupitsyn created IGNITE-6494:
--
Summary: .NET: CacheConfiguration.WriteSynchronizationMode
incorrect default value
Key: IGNITE-6494
URL: https://issues.apache.org/jira/browse/IGNITE-6494
Project
On Fri, Sep 22, 2017 at 9:47 AM, Mikhail Cherkasov
wrote:
> Hi all,
>
> I've seen several times that due wrong cache configuration people can't
> find
> data in cache and blame Ignite that it's buggy and doesn't work.
>
> And it's very difficult to find an error in the code, especially if you
> d
Hi Vladimir!
Could you add to future release by PR
(http://apache-ignite-developers.2346864.n4.nabble.com/GitHub-ignite-pull-request-2737-IGNITE-6286-fix-org-h2-jdbc-JdbcSQLException-td22625.html)?
The PR is very important for project Hibernate OGM .
--
Sent from: http://apache-ignite-develop
Vladimir,
Can you please add the configuration example in the ticket?
D.
On Mon, Sep 25, 2017 at 12:20 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Guys,
>
> I suggest we finalize the configuration changes in the original ticket
> then: https://issues.apache.org/jira/browse/IGNIT
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/2739
IGNITE-6360: NPE occurs if object with null indexed field is added
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ig
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2727
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2729
---
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2738
IGNITE-6493 incorrect usage dataStreamer, must be in try-with-resource
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apach
Dmitriy Govorukhin created IGNITE-6493:
--
Summary: IgnitePdsWalTlbTest.testWalDirectOutOfMemory() hangs
Key: IGNITE-6493
URL: https://issues.apache.org/jira/browse/IGNITE-6493
Project: Ignite
Pavel Tupitsyn created IGNITE-6492:
--
Summary: .NET: Tests: Task.Wait should always include a timeout
Key: IGNITE-6492
URL: https://issues.apache.org/jira/browse/IGNITE-6492
Project: Ignite
I
Hi,
For Ignite.NET I would like to include at least these two:
https://issues.apache.org/jira/browse/IGNITE-5615 .NET:
IgniteConfiguration.LocalEventListeners
https://issues.apache.org/jira/browse/IGNITE-4070 .NET: Introduce
transformers to SCAN queries
Also users are asking for .NET Core and L
Hi Vladimir!
Could you please add my PR to next relese. I mean PR
https://github.com/apache/ignite/pull/2737 .
The PR is very important for project Hibernate OGM.
A lot of thanks!
With best regards, Sergey Chernolyas
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
We could even add a configuration switch to throw an exception in such case.
I guess that in majority of use cases there is a single type per cache,
and we should have a way to enforce that.
On Fri, Sep 22, 2017 at 7:47 PM, Mikhail Cherkasov
wrote:
> Hi all,
>
> I've seen several times that due
You can find the list of 2.3 tickets which are either reported by you or
assigned to you using this report [1]. Please make sure that this list is
relevant and tickets will be completed in a matter of 2 weeks.
NB: You should be logged in to JIRA.
[1]
https://issues.apache.org/jira/issues/?jql=pro
GitHub user schernolyas opened a pull request:
https://github.com/apache/ignite/pull/2737
IGNITE-6286: fix org.h2.jdbc.JdbcSQLException
changes:
1) develop test for check all supported types for parameterized queries
2) add support BigDecimal type as type of paraameter's valu
Igniters,
We already fixed 300+ tickets since AI 2.1.0 release. These tickets include
a lot of new features (namely, SQL-related) and usability improvements. Not
to say dozens of important bug fixes. I propose to start planning of AI
2.3.0 release. I think we can deliver it in a month as follows:
Guys,
I suggest we finalize the configuration changes in the original ticket
then: https://issues.apache.org/jira/browse/IGNITE-6030 and proceed with
the changes.
2017-09-23 17:08 GMT+03:00 Dmitriy Setrakyan :
> Can we specify what metrics will look like? I think we should not just
> blindly mer
43 matches
Mail list logo
