Alexander Belyak created IGNITE-6616:
Summary: WebConsole cache config parse
Key: IGNITE-6616
URL: https://issues.apache.org/jira/browse/IGNITE-6616
Project: Ignite
Issue Type: Bug
Igniters, has anyone been able to review yet? Seems like a very useful
feature.
On Wed, Oct 11, 2017 at 1:44 AM, Nikita Amelchev
wrote:
> Hello, Igniters.
>
> I have implemented support for the Externalizable interface in the
> BinaryMarshaller without deserialization on servers.[1,2] I have mad
Absolutely, create a ticket. It would be even better if you picked it up
and contributed a fix :)
On Wed, Oct 11, 2017 at 6:06 AM, Pavel Pereslegin wrote:
> Hello, Igniters.
>
>
> I found that AverageTxCommitTime and AverageTxRollbackTime metrics in
> CacheMetrics calculated in milliseconds inst
On Wed, Oct 11, 2017 at 9:00 AM, ALEKSEY KUZNETSOV wrote:
> Hi, Igntrs!
>
> For suspend\resume operations in pessimistic mode we want to write the same
> tests as for optimistic mode.
>
> What additional tests should we create for the task?
Alexey, I think you should ask the reviewer in the tic
On Thu, Oct 12, 2017 at 7:01 PM, Denis Magda wrote:
> From what I see after running an example they are under the same root
> folder and in different subdirectories. The root folder should be defined
> by setPersistencePath as I guess.
>
If that is the case, then you are right. Then we should no
>From what I see after running an example they are under the same root
folder and in different subdirectories. The root folder should be defined
by setPersistencePath as I guess.
Denis
On Thursday, October 12, 2017, Dmitriy Setrakyan
wrote:
> On Thu, Oct 12, 2017 at 4:05 PM, Denis Magda > wrot
On Wed, Oct 11, 2017 at 11:45 PM, Vladimir Ozerov
wrote:
> Igniters,
>
> We prepared optimization of DML processing. Instead of passing all data
> being updated through the client node, now we can optionally send SQL
> statement to data nodes and perform update locally. This could greatly
> impro
On Thu, Oct 12, 2017 at 4:05 PM, Denis Magda wrote:
> Both terms “persistence” and “storage” mean same to me. If to choose
> between them I would go for “persistence” because this is how
> we name the feature - “Ignite Persistence” [1]
> Furthermore, by default WAL files, the archive and data/i
Igniters,
If to put aside the compilation task [1] on Java 9, nobody can start Ignite
even in the compatibility mode on that version of JDK. That’s the reason [2].
Let’s fix this for 2.3 by expanding the “if” close to -
!U.jdkVersion().contains("1.9"))
Any objections?
[1] https://issues.apach
How about “inPlaceUpdate”?
A side note, I see the feature documented for ODBC in our hidden SQL domain
[1]. But it’s missing for JDBC. Did we forget to update the JDBC docs?
[1]
https://apacheignite-sql.readme.io/docs/connection-string-and-dsn#section-supported-arguments
>
> Unfortunately we
The system properties are a blackbox that few of the users are aware about. How
do we decide where a property should go? Any rule for that?
—
Denis
> On Oct 12, 2017, at 1:43 AM, Alexey Goncharuk
> wrote:
>
> The same way as if one node had cluster name in configuration and the other
> did n
Both terms “persistence” and “storage” mean same to me. If to choose between
them I would go for “persistence” because this is how
we name the feature - “Ignite Persistence” [1].
Furthermore, by default WAL files, the archive and data/index files are located
under the same root which is “setPer
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/2841
GG-12821 IGNITE-4642: Added "enforceJoinOrder" flag to thick JDBC driver.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/2829
---
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2840
Rebalancing optimizations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12001
Alternatively you can revie
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2839
Ignite 1.9.7.b2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.9.7.b2
Alternatively you can review and app
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2838
Ignite 1.9 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.9-master
Alternatively you can review and
Pavel Tupitsyn created IGNITE-6615:
--
Summary: .NET: Thin client: XML configuration
Key: IGNITE-6615
URL: https://issues.apache.org/jira/browse/IGNITE-6615
Project: Ignite
Issue Type: Improve
Github user mcherkasov closed the pull request at:
https://github.com/apache/ignite/pull/2820
---
Dmitry,
In my experience refactoring without a reasons often produces more harm
than benefits. Especially:
1) You may brake compatibility. E.g. moving anonymous inner class to the
top level will cause renames of all other anonymous classes.
2) This may interfere severely with other people's work.
IgniteKernal and some other classes have more places to refactor. At least
for better readable form or to remove inner class [1]. May be create some
tickets for refactoring such complex places? I mean to create main ticket
like [2] or [3], and when someone see something complex *and* the way to
ref
Pavel Tupitsyn created IGNITE-6614:
--
Summary: .NET: DotNetCore examples
Key: IGNITE-6614
URL: https://issues.apache.org/jira/browse/IGNITE-6614
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6613:
--
Summary: .NET: Thin client: Create dotnet core unit test project,
run on Linux
Key: IGNITE-6613
URL: https://issues.apache.org/jira/browse/IGNITE-6613
Project: Ig
Ivan Fedotov created IGNITE-6612:
Summary: Wrap ack methods in their own class
Key: IGNITE-6612
URL: https://issues.apache.org/jira/browse/IGNITE-6612
Project: Ignite
Issue Type: Improvement
Vladimir Ozerov created IGNITE-6611:
---
Summary: Optionally disable binary metadata for type
Key: IGNITE-6611
URL: https://issues.apache.org/jira/browse/IGNITE-6611
Project: Ignite
Issue Type
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/2837
IGNITE-6135
- add new type SQL_DATE(for java.sql.Date class) into the Binary Marshaller.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAm
Vladimir Ozerov created IGNITE-6610:
---
Summary: Unexpected error message 'Duplicate column name' in case
if query has LIMIT
Key: IGNITE-6610
URL: https://issues.apache.org/jira/browse/IGNITE-6610
Pr
Vladimir Ozerov created IGNITE-6609:
---
Summary: H2PkHashIndex.H2Cursor doesn't take in count expiration
Key: IGNITE-6609
URL: https://issues.apache.org/jira/browse/IGNITE-6609
Project: Ignite
Here is the link for the ticket [1] If someone else was wandering
about what kind of optimization we are talking.
[1] - https://issues.apache.org/jira/browse/IGNITE-6024
Best Regards,
Igor
On Thu, Oct 12, 2017 at 9:45 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> We prepared optimization of DML p
Pavel Tupitsyn created IGNITE-6608:
--
Summary: .NET: Thin client documentation
Key: IGNITE-6608
URL: https://issues.apache.org/jira/browse/IGNITE-6608
Project: Ignite
Issue Type: Task
Pavel Tupitsyn created IGNITE-6607:
--
Summary: Thin client: protocol documentation
Key: IGNITE-6607
URL: https://issues.apache.org/jira/browse/IGNITE-6607
Project: Ignite
Issue Type: Task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2835
---
Alexander Belyak created IGNITE-6606:
Summary: Web console agent download
Key: IGNITE-6606
URL: https://issues.apache.org/jira/browse/IGNITE-6606
Project: Ignite
Issue Type: Improvement
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2836
IGNITE-6605
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6605
Alternatively you can review and apply these
Vladimir Ozerov created IGNITE-6605:
---
Summary: SQL: Merge and optimize backup query filter
Key: IGNITE-6605
URL: https://issues.apache.org/jira/browse/IGNITE-6605
Project: Ignite
Issue Type
Alexander Belyak created IGNITE-6604:
Summary: Log exchange progress
Key: IGNITE-6604
URL: https://issues.apache.org/jira/browse/IGNITE-6604
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-6603:
--
Summary: .NET: EntityFramework Core Data Provider
Key: IGNITE-6603
URL: https://issues.apache.org/jira/browse/IGNITE-6603
Project: Ignite
Issue Type: Imp
The same way as if one node had cluster name in configuration and the other
did not - they should not discover each other.
2017-10-12 11:40 GMT+03:00 Alexey Kuznetsov :
> Alexey,
>
> How we would handle situation if first node has one name in sys props and
> second has another name or does not ha
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/2835
IGNITE-5928 .NET: Get rid of BinaryStreamBase
Please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5928
Alexey,
How we would handle situation if first node has one name in sys props and
second has another name or does not have any name?
On Thu, Oct 12, 2017 at 3:19 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Personally, I would still add an ability to set cluster name via the syste
Personally, I would still add an ability to set cluster name via the system
property because in some cases this may be convenient (starting multiple
clusters with the same configuration from ignite.sh, embedded deployments
when configuration change is not available).
--AG
2017-10-11 14:13 GMT+03:
Name *setPersistencePath* looks confusing to me because both WAL and
index/partition files storage provide persistence. That's why we
separated API methods as *setWalPath* and *setStoragePath*.
I think, *setStoragePath* is good enough as long as it's supported by
explaining javadoc.*
*
Best Re
42 matches
Mail list logo