Roman Shtykh created IGNITE-6042:
Summary: Update KafkaStreamer dependencies to Kafka 0.11.x
Key: IGNITE-6042
URL: https://issues.apache.org/jira/browse/IGNITE-6042
Project: Ignite
Issue
Igniters,
I have filed several website tickets to reflect the addition of persistence
in the latest 2.1 release:
https://issues.apache.org/jira/browse/IGNITE-6036
https://issues.apache.org/jira/browse/IGNITE-6037
https://issues.apache.org/jira/browse/IGNITE-6038
Dmitriy Setrakyan created IGNITE-6041:
-
Summary: Update Gettting Started documentation page
Key: IGNITE-6041
URL: https://issues.apache.org/jira/browse/IGNITE-6041
Project: Ignite
Issue
Dmitriy Setrakyan created IGNITE-6040:
-
Summary: Update Distributed SQL Database page on the website
Key: IGNITE-6040
URL: https://issues.apache.org/jira/browse/IGNITE-6040
Project: Ignite
Dmitriy Setrakyan created IGNITE-6039:
-
Summary: Update Persistence page on the website
Key: IGNITE-6039
URL: https://issues.apache.org/jira/browse/IGNITE-6039
Project: Ignite
Issue
Dmitriy Setrakyan created IGNITE-6038:
-
Summary: Update Data Grid page on teh website to reflect
Persistence
Key: IGNITE-6038
URL: https://issues.apache.org/jira/browse/IGNITE-6038
Project:
Dmitriy Setrakyan created IGNITE-6037:
-
Summary: Ignite 2.1 features overview changes on the website
Key: IGNITE-6037
URL: https://issues.apache.org/jira/browse/IGNITE-6037
Project: Ignite
Dmitriy Setrakyan created IGNITE-6036:
-
Summary: Ignite 2.1 use case changes on the website
Key: IGNITE-6036
URL: https://issues.apache.org/jira/browse/IGNITE-6036
Project: Ignite
Issue
Denis,
This only allows to limit dataset fetched from DB to Spark. This is useful,
but does not replace custom Strategy integration. Because after you create
the FD, you will use its API to do additional filtering, mapping,
aggregation, etc., and this will happen within Spark. With custom
>> This JDBC integration is just a Spark data source, which means that Spark
>> will fetch data in its local memory first, and only then apply filters,
>> aggregations, etc.
Seems that there is a backdoor exposed via the standard SQL syntax. You can
execute so called “pushdown” queries [1] that
Folks,
I noticed that the latest successful nightly build happened on May 31:
https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSuccessfulBuild/
Looks like it's failing since then. Does anyone know the reason?
-Val
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/2426
---
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
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2432
IGNITE-6034
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6034
Alternatively you can review and apply these
Igor Seliverstov created IGNITE-6035:
Summary: Indexes aren't cleaned on cache clear/destroy
Key: IGNITE-6035
URL: https://issues.apache.org/jira/browse/IGNITE-6035
Project: Ignite
Issue
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2431
IGNITE-6032 ODBC: Added SQL_SCROLL_OPTIONS support for SQLGetInfo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2430
IGNITE-6019
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6019
Alternatively you can review and apply
Vladimir Ozerov created IGNITE-6034:
---
Summary: SQL: Optimize GridQueryNextPageResponse message
consumption
Key: IGNITE-6034
URL: https://issues.apache.org/jira/browse/IGNITE-6034
Project: Ignite
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/2429
IGNITE-6029 WAL Record serialization refactoring
And initial stuff for Record V2 serializer.
You can merge this pull request into a Git repository by running:
$ git pull
If this is true, I think it should be fixed. availablePermits() returning
number of acquired permits sounds very confusing.
-Val
On Thu, Aug 10, 2017 at 7:38 AM, Andrey Kuznetsov wrote:
> Hi, igniters!
>
>
>
> As IgniteSemaphore's javadoc states,
>
>
>
> "Distributed
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/2428
IGNITE-4991 Do not print out system properties when IGNITE_TO_STRING_â¦
â¦INCLUDE_SENSITIVE is set to false
You can merge this pull request into a Git repository by running:
$ git pull
Ivan Rakov created IGNITE-6033:
--
Summary: Add sorted and multithreaded modes in checkpoint algorithm
Key: IGNITE-6033
URL: https://issues.apache.org/jira/browse/IGNITE-6033
Project: Ignite
Igor Sapego created IGNITE-6032:
---
Summary: ODBC: SQLGetData should return SQL_SUCCESS if called on
NULL column
Key: IGNITE-6032
URL: https://issues.apache.org/jira/browse/IGNITE-6032
Project: Ignite
GitHub user vadopolski opened a pull request:
https://github.com/apache/ignite/pull/2427
Ignite 4756
Added calculate printDistribution method and
AffinityDistributionPrintLogTest.
You can merge this pull request into a Git repository by running:
$ git pull
Vica Abramova created IGNITE-6031:
-
Summary: Web Console: Improve grouping of fields on Cluster
Configuration Tab (By importance / alphabetically)
Key: IGNITE-6031
URL:
Going down "node set" road:
-fixed node set
-established node set
-base node set
On Thu, Aug 10, 2017 at 5:23 PM, Dmitriy Setrakyan
wrote:
> Can we brainstorm on the names again, I am not sure we have a consensus on
> the name "baseline topology". This will be included
Hi, igniters!
As IgniteSemaphore's javadoc states,
"Distributed semaphore provides functionality similar to {@code
java.util.concurrent.Semaphore}."
At the same time method semantics of current implementation is inverted,
i.e. acquire() decrements internal semaphore count and
Can we brainstorm on the names again, I am not sure we have a consensus on
the name "baseline topology". This will be included in Ignite
configuration, so the name has to be clear.
Some of the proposals were:
- baseline topology
- minimal node set
- node restart set
- minimal topology
Any other
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2426
IGNITE-6027
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6027
Alternatively you can review and apply these
Alexey Goncharuk created IGNITE-6030:
Summary: Allow enabling persistence per-cache
Key: IGNITE-6030
URL: https://issues.apache.org/jira/browse/IGNITE-6030
Project: Ignite
Issue Type:
Pavel Kovalenko created IGNITE-6029:
---
Summary: Refactor WAL Record serialization and introduce
RecordV2Serializer
Key: IGNITE-6029
URL: https://issues.apache.org/jira/browse/IGNITE-6029
Project:
Taras Ledkov created IGNITE-6028:
Summary: JDBC thin Driver: support metadata getFunctions methods
Key: IGNITE-6028
URL: https://issues.apache.org/jira/browse/IGNITE-6028
Project: Ignite
Vladimir Ozerov created IGNITE-6027:
---
Summary: SQL: add "last" flag to GridQueryNextPageResponse
Key: IGNITE-6027
URL: https://issues.apache.org/jira/browse/IGNITE-6027
Project: Ignite
Hi Alex,
The main idea from the API perspective is that Ignite Persistence is
transparent for the API. After you enable persistence all your APIs including
get/put, SQL, etc would work as before.
Enable Persistence with 1 line:
And then activate cluster explicitly - With script:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2422
---
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
Alex Negashev created IGNITE-6026:
-
Summary: init cluster for Ignite Ignite Persistence by xml
Key: IGNITE-6026
URL: https://issues.apache.org/jira/browse/IGNITE-6026
Project: Ignite
Issue
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/2421
---
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
Vladimir Ozerov created IGNITE-6025:
---
Summary: SQL: improve CREATE INDEX performance
Key: IGNITE-6025
URL: https://issues.apache.org/jira/browse/IGNITE-6025
Project: Ignite
Issue Type:
Denis,
This should be handled by the BT triggers. If I have 3 backups configured,
I actually won't care if my cluster will live 6 hours without an additional
backup. If for a partition there is only one backup left - a new BT should
be triggered automatically.
2017-08-10 0:33 GMT+03:00 Denis
Vladimir Ozerov created IGNITE-6024:
---
Summary: SQL: execute DML statements on the server when possible
Key: IGNITE-6024
URL: https://issues.apache.org/jira/browse/IGNITE-6024
Project: Ignite
Vladimir Ozerov created IGNITE-6023:
---
Summary: Index inline should be enabled by default for
fixed-length data types
Key: IGNITE-6023
URL: https://issues.apache.org/jira/browse/IGNITE-6023
Project:
Vladimir Ozerov created IGNITE-6022:
---
Summary: SQL: add native batch execution support for DML statements
Key: IGNITE-6022
URL: https://issues.apache.org/jira/browse/IGNITE-6022
Project: Ignite
Vladimir Ozerov created IGNITE-6021:
---
Summary: SQL: support asynchronous page prefetch on client side
Key: IGNITE-6021
URL: https://issues.apache.org/jira/browse/IGNITE-6021
Project: Ignite
Vladimir Ozerov created IGNITE-6020:
---
Summary: SQL: client should request first pages on query execution
instead of first cursor read
Key: IGNITE-6020
URL: https://issues.apache.org/jira/browse/IGNITE-6020
Vladimir Ozerov created IGNITE-6019:
---
Summary: SQL: client node should not hold the whole data set
in-memory when possible
Key: IGNITE-6019
URL: https://issues.apache.org/jira/browse/IGNITE-6019
44 matches
Mail list logo