Vladimir,
> When we finish varlen optimization for string lengths, I am afraid we
could
> end up with very messy protocol, should we mix encoded length and
encoding.
I agree, we shouldn't mix it.
> I deemed it's unusual to make two differerent type markers (flags) for
> single datatype. I can't se
Sergey Chugunov created IGNITE-5839:
---
Summary: Unclear exception from BinaryObjectBuilder::build call
when builder is reused
Key: IGNITE-5839
URL: https://issues.apache.org/jira/browse/IGNITE-5839
P
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/2150
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Konstantin,
Ok, no objections from my side. I need some times for read documentation. I
hope we will finished in two weeks.
http://reviews.ignite.apache.org - will setup for ssl using too.
Konstantin Boudnik-2 wrote
> I have never heard about this provider, and it is great they are donating
>
Denis,
Added you to the contributors list.
2017-07-25 16:04 GMT+03:00 Denis Mekhanikov :
> My JIRA ID: dmekhanikov
>
> Thank you!
>
> вт, 25 июл. 2017 г. в 15:09, Dmitry Pavlov :
>
> > Hi Denis,
> >
> > Welcome to the Ignite community!
> >
> > If you need contributor access to Apache JIRA, could
We still need to confirm the correct behavior:
1) Should it be possible to call Transaction.close() from a different
thread?
2) Do we need to call close() after commit()? What about commitAsync()?
What if exception happens?
Can someone clarify this?
On Tue, Jul 25, 2017 at 11:08 PM, Nikolay Izhik
close() for Transaction is a method inherited from AutoCloseable.
It used to rollback tx in case it was not rollbacked or commited inside try
section
here's the code of close:
@Override public void close() throws IgniteCheckedException {
TransactionState state = state();
if (stat
Dmitry Karachentsev created IGNITE-5840:
---
Summary: IgniteUuid could not be used as a cache key
Key: IGNITE-5840
URL: https://issues.apache.org/jira/browse/IGNITE-5840
Project: Ignite
Is
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/2346
IGNITE-5840 - Reproducer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5840
Alternatively you can review
Thanks a lot!
ср, 26 июл. 2017 г. в 12:42, Alexey Goncharuk :
> Denis,
>
> Added you to the contributors list.
>
> 2017-07-25 16:04 GMT+03:00 Denis Mekhanikov :
>
> > My JIRA ID: dmekhanikov
> >
> > Thank you!
> >
> > вт, 25 июл. 2017 г. в 15:09, Dmitry Pavlov :
> >
> > > Hi Denis,
> > >
> > > We
Dmitriy Pavlov created IGNITE-5841:
--
Summary: Ignite SPI Suite: testReconnectAfterFailTopologyChanged()
test failure with assertions
Key: IGNITE-5841
URL: https://issues.apache.org/jira/browse/IGNITE-5841
Val,
AFAIK, affinityRun/Call has guarantee to be successfully executed on
unstable topology in case partition was not losed, only relocated to
another node during rebalancing.
On Tue, Jul 25, 2017 at 10:44 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Alexey,
>
> Is there exa
Igor Sapego created IGNITE-5842:
---
Summary: ODBC: Make sure ODBC driver works correctly with RazorSQL.
Key: IGNITE-5842
URL: https://issues.apache.org/jira/browse/IGNITE-5842
Project: Ignite
Iss
Hello folks,
Recently I filed a ticket [1] with very simple test where correct usage of
BinaryObjectBuilder is vague.
The issue boils down to the fact that it is unclear from documentation and
behavior whether reusing of BinaryObjectBuilder is allowed.
Let's discuss here what is the correct beha
Eduard Shangareev created IGNITE-5843:
-
Summary: Ignite PDS: We don't save cache configuration if we get
it on join
Key: IGNITE-5843
URL: https://issues.apache.org/jira/browse/IGNITE-5843
Project:
Hello, Igniters.
I'm working on IGNITE-425 [1] issue.
I made a couple of changes in my branch [2] so I want to confirm that
changes with community before moving forward:
Text of issue:
```
Currently if updated entry passes the filter, it is sent to node initiated
the query entirely.
It would be
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/2347
IGNITE-5843 Ignite PDS: We don't save cache configuration if we get iâ¦
â¦t on join
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain
Hi,
Currently tx is AutoCloseable and 'close' should be always called by
interface contract.
Currently Transaction is single-threaded and should not be used by multiple
concurrent threads. But if you call commitAsync and then call 'close' from
commitAsync listener this is correct usage and we sho
Hello, Semyon.
Thank you for your clarification.
I removed check for threadId from my pull request.
2017-07-26 16:52 GMT+03:00 Semyon Boikov :
> Hi,
>
> Currently tx is AutoCloseable and 'close' should be always called by
> interface contract.
>
> Currently Transaction is single-threaded and sho
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2335
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2348
IGNITE-5771: Added Ignite::SetActive() for C++
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5771
Alternativel
Vladimir,
It's rather simple to support string encoding by setting it in
BinaryConfiguration. But I'm unsure whether it's a desired change. We need
to express our goal more precisely: should we control encoding at cache
level, field level, or binary configuration level? Currently,
BinaryMarshaller
GitHub user asfedotov opened a pull request:
https://github.com/apache/ignite/pull/2349
IGNITE-4172 SQL: Add support for Java 8 Time API classes in date\time
functions
For CI purposes only.
You can merge this pull request into a Git repository by running:
$ git pull https://gi
Yury Babak created IGNITE-5844:
--
Summary: Distributed versions of matrix decompositions
Key: IGNITE-5844
URL: https://issues.apache.org/jira/browse/IGNITE-5844
Project: Ignite
Issue Type: New Fe
Yury Babak created IGNITE-5845:
--
Summary: Benchmarks for ML algorithms.
Key: IGNITE-5845
URL: https://issues.apache.org/jira/browse/IGNITE-5845
Project: Ignite
Issue Type: Improvement
Yury Babak created IGNITE-5846:
--
Summary: Add support of distributed matrices for OLS regression.
Key: IGNITE-5846
URL: https://issues.apache.org/jira/browse/IGNITE-5846
Project: Ignite
Issue Ty
Yury Babak created IGNITE-5847:
--
Summary: API for Models
Key: IGNITE-5847
URL: https://issues.apache.org/jira/browse/IGNITE-5847
Project: Ignite
Issue Type: New Feature
Components: ml
Nikolay Tikhonov created IGNITE-5848:
Summary: Ignite should support Hibernate 5.2.X
Key: IGNITE-5848
URL: https://issues.apache.org/jira/browse/IGNITE-5848
Project: Ignite
Issue Type: Su
On Wed, Jul 26, 2017 at 3:40 AM, Vyacheslav Daradur
wrote:
>
> > Encoding must be set on per field basis. This will give us as most
> flexible
> > solution at the cost of 1-byte overhead.
>
> > Vova, I agree that the encoding should be set on per-field basis, but at
> > the table level, not at a
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/2350
IGNITE-5218: Column-based decision trees implemented.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5218
A
Nikolay,
We already have the following method for queries with transformer. It
currently throws exception for ContinuousQuery.
QueryCursor query(Query qry, IgniteClosure transformer)
Would it be possible to utilize it instead of creating new API?
-Val
On Wed, Jul 26, 2017 at 5:26 AM, Николай
Anton,
This seems to be a completely separate issue. I don't see how it can be
fixed by adding new APIs.
-Val
On Wed, Jul 26, 2017 at 3:56 AM, Anton Vinogradov
wrote:
> Val,
>
> AFAIK, affinityRun/Call has guarantee to be successfully executed on
> unstable topology in case partition was not l
Good point! Thanks! Please let me know if you need any assistance from me
--
With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company t
Hi,
We need to decide what сhecksum algorythm we should use for signing release
artifacts. Currently we use md5 and sha-1. sha-1 will be replaced by
sha-256 soon. Should we keep md5 or use only sha-256?
Hi Oleg,
Both MD5 and SHA1 are deprecated and can't be considered as trustfull.
I think at-least-256 bit member of the SHA-2 family (e. g. sha512) should
be used.
Sincerely,
Dmitriy Pavlov
ср, 26 июл. 2017 г. в 22:27, Oleg Ostanin :
> Hi,
>
> We need to decide what сhecksum algorythm we should
Folks of the valley, Bay Area and San-Francisco come over to community’s meetup
(https://www.meetup.com/Bay-Area-In-Memory-Computing/events/241381155/) to
learn more about the internals of durable memory architecture and Ignite
Persistent Store that will be released in Apache Ignite 2.1 througho
Yeah, unfortunately current ContinuousQuery object can be used for querying
with transformer. That's actually not good, because adding transformers to
continuous queries and scan queries will be very inconsistent.
AFAIK, there are plans to completely rework query API since we added a lot
of stuff
+1 (binding)
—
Denis
> On Jul 24, 2017, at 6:32 AM, Anton Vinogradov wrote:
>
> Igniters,
>
> This vote based on same files as RC3.
> Only one change is that I signed zips with my signature.
> KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS) was
> updated as well.
>
> We al
38 matches
Mail list logo
