1.5.final
Locked
12
12
 
|
Hi Igniters
We've great progress and only two outstanding issues prevents to release: IGNITE-2252 Add support for cache sql schema in REST topology command <https://issues.apache.org/jira/browse/IGNITE-2252> IGNITE-2175 Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7) <https://issues.apache.org/jira/browse/IGNITE-2175> On Wed, Dec 23, 2015 at 3:10 PM, Alexey Goncharuk < [hidden email]> wrote: > The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been > merged to ignite-1.5 > -- Sergey Kozlov |
|
|
I think "IGNITE-2252 Add support for cache sql schema in REST topology
command" will be fixed tomorrow in first half of a day. On Wed, Dec 23, 2015 at 7:14 PM, Sergey Kozlov <[hidden email]> wrote: > Hi Igniters > We've great progress and only two outstanding issues prevents to release: > IGNITE-2252 Add support for cache sql schema in REST topology command > <https://issues.apache.org/jira/browse/IGNITE-2252> > IGNITE-2175 Not valid exceptions in case when example can't works with > remote node started with server classpath (Java 7) > <https://issues.apache.org/jira/browse/IGNITE-2175> > > > > On Wed, Dec 23, 2015 at 3:10 PM, Alexey Goncharuk < > [hidden email]> wrote: > > > The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been > > merged to ignite-1.5 > > > > > > -- > Sergey Kozlov > -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
|
|
The fix for https://issues.apache.org/jira/browse/IGNITE-2175 has been
merged to ignite-1.5 On Wed, Dec 23, 2015 at 4:30 PM, Alexey Kuznetsov <[hidden email]> wrote: > I think "IGNITE-2252 Add support for cache sql schema in REST topology > command" will be fixed tomorrow in first half of a day. > > On Wed, Dec 23, 2015 at 7:14 PM, Sergey Kozlov <[hidden email]> > wrote: > > > Hi Igniters > > We've great progress and only two outstanding issues prevents to release: > > IGNITE-2252 Add support for cache sql schema in REST topology command > > <https://issues.apache.org/jira/browse/IGNITE-2252> > > IGNITE-2175 Not valid exceptions in case when example can't works with > > remote node started with server classpath (Java 7) > > <https://issues.apache.org/jira/browse/IGNITE-2175> > > > > > > > > On Wed, Dec 23, 2015 at 3:10 PM, Alexey Goncharuk < > > [hidden email]> wrote: > > > > > The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been > > > merged to ignite-1.5 > > > > > > > > > > > -- > > Sergey Kozlov > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > |
|
In reply to this post by Alexey Kuznetsov-2
On Wed, Dec 23, 2015 at 5:30 AM, Alexey Kuznetsov <[hidden email]>
wrote: > I think "IGNITE-2252 Add support for cache sql schema in REST topology > command" will be fixed tomorrow in first half of a day. > This looks like an old issue. Is there a reason why this ticket is so critical for 1.5 release? |
|
|
No, this is not old issue, new cache configuration property "SQL schema"
was merged into ignite-1.5 two days ago. I would like to fix in ignite-1.5 in order to be able to execute SQL queries from Ignite console against ignite-1.5 cluster. New "SQL schema" cache configuration property implemented in such a way that if user specify it then cache name can not be used as "schema name" any more only specified schema name. So, we need to show sql schema on web console UI and use it for building SQL queries. Please, take a look at this thread http://apache-ignite-developers.2346864.n4.nabble.com/sqlSchema-usability-question-td6133.html Where sql schema usability was discussed. On Thu, Dec 24, 2015 at 12:14 AM, Dmitriy Setrakyan <[hidden email]> wrote: > On Wed, Dec 23, 2015 at 5:30 AM, Alexey Kuznetsov <[hidden email] > > > wrote: > > > I think "IGNITE-2252 Add support for cache sql schema in REST topology > > command" will be fixed tomorrow in first half of a day. > > > > This looks like an old issue. Is there a reason why this ticket is so > critical for 1.5 release? > -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
|
|
Got it. Looks like this is the only remaining issue. Please let us know
here once you fix it, so we could start voting on the final release. On Wed, Dec 23, 2015 at 9:22 AM, Alexey Kuznetsov <[hidden email]> wrote: > No, this is not old issue, new cache configuration property "SQL schema" > was merged into ignite-1.5 two days ago. > > I would like to fix in ignite-1.5 in order to be able to execute SQL > queries from Ignite console against ignite-1.5 cluster. > > New "SQL schema" cache configuration property implemented in such a way > that if user specify it > then cache name can not be used as "schema name" any more only specified > schema name. > > So, we need to show sql schema on web console UI and use it for building > SQL queries. > > Please, take a look at this thread > > http://apache-ignite-developers.2346864.n4.nabble.com/sqlSchema-usability-question-td6133.html > Where sql schema usability was discussed. > > On Thu, Dec 24, 2015 at 12:14 AM, Dmitriy Setrakyan <[hidden email] > > > wrote: > > > On Wed, Dec 23, 2015 at 5:30 AM, Alexey Kuznetsov < > [hidden email] > > > > > wrote: > > > > > I think "IGNITE-2252 Add support for cache sql schema in REST topology > > > command" will be fixed tomorrow in first half of a day. > > > > > > > This looks like an old issue. Is there a reason why this ticket is so > > critical for 1.5 release? > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > |
|
|
IGNITE-2252 Add support for cache sql schema in REST topology command
Fixed, tested, docs updated and merged into release branch. -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
|
|
Hi
It's the last ticket from the list provided yesterday. But today we found yet another blocker issue and now we're working on it: IGNITE-2257 Incorrect deserialization of BinaryContext. <https://issues.apache.org/jira/browse/IGNITE-2257> On Thu, Dec 24, 2015 at 2:24 PM, Alexey Kuznetsov <[hidden email]> wrote: > IGNITE-2252 Add support for cache sql schema in REST topology command > > Fixed, tested, docs updated and merged into release branch. > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > -- Sergey Kozlov |
|
|
Igniters,
Another issue has been reported related to unexpected exception in examples when optimized marshaller is used: https://issues.apache.org/jira/browse/IGNITE-2266 I will try to fix this before 2257 is fixed to fit in 1.5, however I do not think it is a blocker for the release. |
|
|
I am seeing that IGNITE-2266 is about Optimized marshaller, not the latest
Binary marshaling which should be used by default. Any reason we care about Optimized marshaller for the examples? D. On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk < [hidden email]> wrote: > Igniters, > > Another issue has been reported related to unexpected exception in examples > when optimized marshaller is used: > https://issues.apache.org/jira/browse/IGNITE-2266 > > I will try to fix this before 2257 is fixed to fit in 1.5, however I do not > think it is a blocker for the release. > |
|
|
It is the way to test optimized marshaller.
The binary marshaller is a new feature and not very well tested yet thus optimized marshalling shouldn't be broken for any cases On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan <[hidden email]> wrote: > I am seeing that IGNITE-2266 is about Optimized marshaller, not the latest > Binary marshaling which should be used by default. Any reason we care about > Optimized marshaller for the examples? > > D. > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk < > [hidden email]> wrote: > > > Igniters, > > > > Another issue has been reported related to unexpected exception in > examples > > when optimized marshaller is used: > > https://issues.apache.org/jira/browse/IGNITE-2266 > > > > I will try to fix this before 2257 is fixed to fit in 1.5, however I do > not > > think it is a blocker for the release. > > > -- Sergey Kozlov GridGain Systems www.gridgain.com |
|
|
If the examples work well with BinaryMarshaller, I think we can push this
ticket to 1.6. Thoughts? On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov <[hidden email]> wrote: > It is the way to test optimized marshaller. > The binary marshaller is a new feature and not very well tested yet thus > optimized marshalling shouldn't be broken for any cases > > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan <[hidden email]> > wrote: > > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the > latest > > Binary marshaling which should be used by default. Any reason we care > about > > Optimized marshaller for the examples? > > > > D. > > > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk < > > [hidden email]> wrote: > > > > > Igniters, > > > > > > Another issue has been reported related to unexpected exception in > > examples > > > when optimized marshaller is used: > > > https://issues.apache.org/jira/browse/IGNITE-2266 > > > > > > I will try to fix this before 2257 is fixed to fit in 1.5, however I do > > not > > > think it is a blocker for the release. > > > > > > > > > -- > Sergey Kozlov > GridGain Systems > www.gridgain.com > |
|
|
Yes, sure.
On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan <[hidden email]> wrote: > If the examples work well with BinaryMarshaller, I think we can push this > ticket to 1.6. Thoughts? > > On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov <[hidden email]> > wrote: > > > It is the way to test optimized marshaller. > > The binary marshaller is a new feature and not very well tested yet thus > > optimized marshalling shouldn't be broken for any cases > > > > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan < > [hidden email]> > > wrote: > > > > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the > > latest > > > Binary marshaling which should be used by default. Any reason we care > > about > > > Optimized marshaller for the examples? > > > > > > D. > > > > > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk < > > > [hidden email]> wrote: > > > > > > > Igniters, > > > > > > > > Another issue has been reported related to unexpected exception in > > > examples > > > > when optimized marshaller is used: > > > > https://issues.apache.org/jira/browse/IGNITE-2266 > > > > > > > > I will try to fix this before 2257 is fixed to fit in 1.5, however I > do > > > not > > > > think it is a blocker for the release. > > > > > > > > > > > > > > > -- > > Sergey Kozlov > > GridGain Systems > > www.gridgain.com > > > -- Sergey Kozlov GridGain Systems www.gridgain.com |
|
|
Hi
Last issue has been fixed and we started to prepare the release Apache Ignite 1.5 On Thu, Dec 24, 2015 at 8:12 PM, Sergey Kozlov <[hidden email]> wrote: > Yes, sure. > > On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan <[hidden email]> > wrote: > >> If the examples work well with BinaryMarshaller, I think we can push this >> ticket to 1.6. Thoughts? >> >> On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov <[hidden email]> >> wrote: >> >> > It is the way to test optimized marshaller. >> > The binary marshaller is a new feature and not very well tested yet thus >> > optimized marshalling shouldn't be broken for any cases >> > >> > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan < >> [hidden email]> >> > wrote: >> > >> > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the >> > latest >> > > Binary marshaling which should be used by default. Any reason we care >> > about >> > > Optimized marshaller for the examples? >> > > >> > > D. >> > > >> > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk < >> > > [hidden email]> wrote: >> > > >> > > > Igniters, >> > > > >> > > > Another issue has been reported related to unexpected exception in >> > > examples >> > > > when optimized marshaller is used: >> > > > https://issues.apache.org/jira/browse/IGNITE-2266 >> > > > >> > > > I will try to fix this before 2257 is fixed to fit in 1.5, however >> I do >> > > not >> > > > think it is a blocker for the release. >> > > > >> > > >> > >> > >> > >> > -- >> > Sergey Kozlov >> >> > >> > > > > -- > Sergey Kozlov > > -- Sergey Kozlov |
|
|
On Thu, Dec 24, 2015 at 11:23 PM, Sergey Kozlov <[hidden email]>
wrote: > Hi > > Last issue has been fixed and we started to prepare the release > Apache Ignite 1.5 > Great news! Thanks, everyone, for the effort put in. Looking forward to the final release. > > > On Thu, Dec 24, 2015 at 8:12 PM, Sergey Kozlov <[hidden email]> > wrote: > > > Yes, sure. > > > > On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan < > [hidden email]> > > wrote: > > > >> If the examples work well with BinaryMarshaller, I think we can push > this > >> ticket to 1.6. Thoughts? > >> > >> On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov <[hidden email]> > >> wrote: > >> > >> > It is the way to test optimized marshaller. > >> > The binary marshaller is a new feature and not very well tested yet > thus > >> > optimized marshalling shouldn't be broken for any cases > >> > > >> > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan < > >> [hidden email]> > >> > wrote: > >> > > >> > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the > >> > latest > >> > > Binary marshaling which should be used by default. Any reason we > care > >> > about > >> > > Optimized marshaller for the examples? > >> > > > >> > > D. > >> > > > >> > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk < > >> > > [hidden email]> wrote: > >> > > > >> > > > Igniters, > >> > > > > >> > > > Another issue has been reported related to unexpected exception in > >> > > examples > >> > > > when optimized marshaller is used: > >> > > > https://issues.apache.org/jira/browse/IGNITE-2266 > >> > > > > >> > > > I will try to fix this before 2257 is fixed to fit in 1.5, however > >> I do > >> > > not > >> > > > think it is a blocker for the release. > >> > > > > >> > > > >> > > >> > > >> > > >> > -- > >> > Sergey Kozlov > >> > >> > > >> > > > > > > > > -- > > Sergey Kozlov > > > > > > > -- > Sergey Kozlov > |
«
Return to Apache Ignite Developers - Legacy Mail Archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |