Folks,
Based on user's feedback about beta of 1.5, I created several tickets for
binary marshaller that should be fixed in the final version. Here is the
list:
- https://issues.apache.org/jira/browse/IGNITE-2098
- https://issues.apache.org/jira/browse/IGNITE-2099
- https://issues.apache.
Valentin Kulichenko created IGNITE-2100:
---
Summary: Queries do not work with binary marshaller and
Externalizable objects
Key: IGNITE-2100
URL: https://issues.apache.org/jira/browse/IGNITE-2100
P
Valentin Kulichenko created IGNITE-2099:
---
Summary: Binary marshaller writes any map as a HashMap
Key: IGNITE-2099
URL: https://issues.apache.org/jira/browse/IGNITE-2099
Project: Ignite
Valentin Kulichenko created IGNITE-2098:
---
Summary: Need to check that Java Proxy is properly (de)serialized
with binary marshaller
Key: IGNITE-2098
URL: https://issues.apache.org/jira/browse/IGNITE-2098
I filed https://issues.apache.org/jira/browse/IGNITE-2097
On Tue, Dec 8, 2015 at 12:02 AM, Dmitriy Setrakyan
wrote:
> I completely agree. We should make our SQL capabilities more prominent and
> visible. Sergey, can you file a ticket for this outlining what changes need
> to take place?
>
> D.
>
Sergey Kozlov created IGNITE-2097:
-
Summary: Splitting Query example
Key: IGNITE-2097
URL: https://issues.apache.org/jira/browse/IGNITE-2097
Project: Ignite
Issue Type: Task
Compone
Valentin Kulichenko created IGNITE-2096:
---
Summary: AtomicConfiguration and CollectionConfiguration should be
properly checked for consistency
Key: IGNITE-2096
URL: https://issues.apache.org/jira/browse/IGNIT
Valentin Kulichenko created IGNITE-2095:
---
Summary: SpringCacheManager doesn't support withKeepBinary() flag
Key: IGNITE-2095
URL: https://issues.apache.org/jira/browse/IGNITE-2095
Project: Ignite
Folks,
I just noticed that NearCacheConfiguration class extends JCache's
MutableConfiguration. This means that it inherits properties like
writeThrough, readThrough, etc., which doesn't look right to me.
Was it done on purpose? Does anyone know the reason?
-Val
Ken, we already working on it.
See: https://issues.apache.org/jira/browse/IGNITE-843
Sources will be released in ignite-1.6
Also we have beta-version with hosting sponsored by GridGain:
console.gridgain.com
On Tue, Dec 8, 2015 at 9:11 AM, Ken Cheng wrote:
> Is there any plan to build an ignit
Is there any plan to build an ignite web console? The similar web
application as hazcalst.
Thanks,
kcheng
On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura wrote:
> Cos,
>
> sepcifies configuration file for Ignite client node that will
> be started during connection establishing by JDBC driver. So this file
> should be available for JDBC driver client.
>
Andrey, should this be documented here?
https://a
I completely agree. We should make our SQL capabilities more prominent and
visible. Sergey, can you file a ticket for this outlining what changes need
to take place?
D.
On Mon, Dec 7, 2015 at 6:45 AM, Sergey Kozlov wrote:
> Hi Igniters
>
> I think queries (SQL) is a killer feature of Ignite. Bu
Konstantin Boudnik created IGNITE-2094:
--
Summary: building the project with 'install' crashes on Mesos
module
Key: IGNITE-2094
URL: https://issues.apache.org/jira/browse/IGNITE-2094
Project: Igni
Cos,
sepcifies configuration file for Ignite client node that will
be started during connection establishing by JDBC driver. So this file
should be available for JDBC driver client.
On Mon, Dec 7, 2015 at 8:59 PM, Konstantin Boudnik wrote:
> Thanks Andrey!
>
> Still a bit unclear: the doc says
If the version is still under development it should be changed to
1.5.0-b2-SNAPSHOT
Cos
On Mon, Dec 07, 2015 at 06:03PM, Sergey Kozlov wrote:
> Hi
>
> Now we released Apache Ignite 1.5.0-b1 and version in branch ignite-1.5
> should changed to 1.5.0-b2
>
> Thoughts?
>
> --
> Sergey Kozlov
Thanks Andrey!
Still a bit unclear: the doc says
" is required and represents any valid URL which points to Ignite
configuration file"
So, that's server side URL then, something like
jdbc:ignite:cfg:///etc/ignite/conf/default-config.xml
assuming that server nodes have said configuration un
On Mon, Dec 07, 2015 at 12:56PM, Anton Vinogradov wrote:
> It's a test release.
> I have no clue why it's located at archive dist.
> It should be removed.
>
> Does anybody know how to remove it?
I think the only way to remove something from archive is by asking infra@ to
do so. Either by a ticket
Alexey Kuznetsov created IGNITE-2093:
Summary: Add support for scan near cache to VisorQueryTask
Key: IGNITE-2093
URL: https://issues.apache.org/jira/browse/IGNITE-2093
Project: Ignite
Is
+1
On Mon, Dec 7, 2015 at 6:03 PM, Sergey Kozlov wrote:
> Hi
>
> Now we released Apache Ignite 1.5.0-b1 and version in branch ignite-1.5
> should changed to 1.5.0-b2
>
> Thoughts?
>
> --
> Sergey Kozlov
>
Hi
Now we released Apache Ignite 1.5.0-b1 and version in branch ignite-1.5
should changed to 1.5.0-b2
Thoughts?
--
Sergey Kozlov
Hi Igniters
I think queries (SQL) is a killer feature of Ignite. But we still have the
example CacheQueryExample where query features provided. What's about to
introduce a new package e.g. called org.apache.ignite.examples.query and
split org.apache.ignite.examples.datagrid.CacheQueryExample into
Hi,
Download page (https://ignite.apache.org/download.cgi) has been updated.
On Mon, Dec 7, 2015 at 3:56 PM, Sergey Kozlov wrote:
> Hi.
>
> Apache Ignite 1.5.0-b1 and its maven staging URL have been released:
>
> https://dist.apache.org/repos/dist/release/ignite/1.5.0-b1/
>
> On Mon, Dec 7, 201
Hi.
Apache Ignite 1.5.0-b1 and its maven staging URL have been released:
https://dist.apache.org/repos/dist/release/ignite/1.5.0-b1/
On Mon, Dec 7, 2015 at 10:28 AM, Dmitriy Setrakyan
wrote:
> Correction: the release has 6 binding votes, not 7. Alexey Kuznetsov is not
> on PMC yet.
>
> Does no
Denis Magda created IGNITE-2092:
---
Summary: Ignite does not recognize the right number of CPU cores
when running under Docker
Key: IGNITE-2092
URL: https://issues.apache.org/jira/browse/IGNITE-2092
Proje
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/299
IGNITE-2065 portable -> binary renaming
https://issues.apache.org/jira/browse/IGNITE-2065
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashut
GitHub user Dmitriyff opened a pull request:
https://github.com/apache/ignite/pull/298
IGNITE-2089 replaced block callout info to static data for templates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Dmitriyff/ignite ignite-2
Dmitriy,
Agree that your solution sounds better. Created a ticket
https://issues.apache.org/jira/browse/IGNITE-2091
Is there anyone in the community who can pick it up and fix the issue
during the nearest month?
--
Denis
On 12/7/2015 8:08 AM, Dmitriy Setrakyan wrote:
I don’t think that usin
Denis Magda created IGNITE-2091:
---
Summary: Service Deployment: use service's class String name
instead of Class during deployment
Key: IGNITE-2091
URL: https://issues.apache.org/jira/browse/IGNITE-2091
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/292
---
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 enab
Igniters (especially Anton and Raul),
Can someone shed a lite on the status of AWS build on TC?
Presently all tests fail with
The AWS Access Key Id you provided does not exist in our records.
What does this mean? Someone configured the build with wrong ID? Can we
just fix it? Or AWS account wit
Pavel Tupitsyn created IGNITE-2090:
---
Summary: .Net: EventsTest.TestSerialization fails
Key: IGNITE-2090
URL: https://issues.apache.org/jira/browse/IGNITE-2090
Project: Ignite
Issue Type: B
Cos,
JDBC driver was reworked in order to use Ignite client node instead of
Ignite Java client. It gives better performance. So now JDBC dirver uses
Ignite xml configuration file using jdbc:ignite:cfg protocol. See
documentation for version 1.4
https://apacheignite.readme.io/v1.4/docs/jdbc-driver
It's a test release.
I have no clue why it's located at archive dist.
It should be removed.
Does anybody know how to remove it?
On Mon, Dec 7, 2015 at 7:18 AM, Konstantin Boudnik wrote:
> Forking of the release schema conversation. I have noticed that official
> dist
> http://archive.apache
34 matches
Mail list logo
