July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3175) Upgrade the java hotrod client to support remote querying

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3175?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3175: -------------------------------- Fix Version/s: 6.0.0.Alpha2 6.0.0.Final > Upgrade the java hotrod client to support remote querying > --------------------------------------------------------- > > Key: ISPN-3175 > URL: https://issues.jboss.org/browse/ISPN-3175 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Once we'll have ISPN-3169(define query fluent API), ISPN-3173(add a new query operation over hotrod) and ISPN-3174(String-based query language) in place, this is about connecting the dots: invoke the remote query on the server and present the result to the user. > h3.On the client side > As described in ISPN-3173, the query is sent as a byte[] to the server: the payload. > The request payload is query specific (not defined in the HR protocol) and at this stage has the following format: [Q_TYPE] [QUERY_ST] [FIRST_INDEX] [PAGE_SIZE]. This format accommodates the remote query requirements as defined in ISPN-3169. > - Q_TYPE (protobuf's byte) and query identifier, 1 for JPAQL (this is the query type we'll support). In future we'll add different query types as well. > - QUERY_STRING (protobuf's string)- JPAQL string generated by the fluent API (ISPN-3169). Parameters are encoded in this string (vs being sent separately) > - FIRST_INDEX + PAGE_SIZE (protobuf's int)- used for paginating/iterating over the result set. > HR response: [HR_SUCESS_FLAG] [payload] > PAYLOAD = [NUM_EL] [PROJ_SIZE] [ELEMENTS] > - even though at this stage we don't support projections (see ISPN-3169) PROJ_SIZE is added for future compatibility when projection will be supported. > Note that the payload for both request and response should be marshalled with protobuf as this information is read/written over multiple clients. > h3.On the server side > - the server module reads the query operation and the payload (byte[]) > - invokes QueryFacade.query(byte[]) : byte[] > - QueryFacade is an interface defined in the server modules > - has an implementation in the remote-query module (new modules) > - the reason for adding this module: RemoteQueryImpl cannot be in the server modules (ASL) as it has a dependency on the query module (LGPL) which would "contaminate" the server module. Another option would be to merge it in the query module itself, but doesn't feel like a natural fit as its responsibility is serializing data (protobuf). OTOH if it is small we can merge it there so that we don't add a new module to the system? > > For an overview on the remote querying see https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1307) REST protocol improvements for version 2

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1307?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1307: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > REST protocol improvements for version 2 > ---------------------------------------- > > Key: ISPN-1307 > URL: https://issues.jboss.org/browse/ISPN-1307 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: REST > > This JIRA is meant to act as an umbrella for improvements we might want to do in the REST protocol. For example: > - As shown in ISPN-1285 and https://docs.jboss.org/author/display/ISPN/Accessing+data+in+Infinispan+v..., the use of 0 as timeToLiveSeconds and/or maxIdleTimeSeconds parameter(s) is not very intuitive and it's not even symmetric. This should be sorted out. This has been highlighted again in ISPN-1425. One option could be to use -2 as @DefaultValue in order to distinguish between no values given and other options. > This JIRA should also figure out how to support multiple REST protocol versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-203) REST interface to Infinispan DB

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-203?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-203: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > REST interface to Infinispan DB > ------------------------------- > > Key: ISPN-203 > URL: https://issues.jboss.org/browse/ISPN-203 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Michael Neale > Assignee: Manik Surtani > > As described here: http://www.jboss.org/community/wiki/InfinispanDB > This will build on (or perhaps be built in) the server/rest module - as well as some additions of helper classes to core, and a query language to query module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3175) Upgrade the java hotrod client to support remote querying

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3175?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3175: -------------------------------- Priority: Blocker (was: Major) > Upgrade the java hotrod client to support remote querying > --------------------------------------------------------- > > Key: ISPN-3175 > URL: https://issues.jboss.org/browse/ISPN-3175 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Priority: Blocker > > Once we'll have ISPN-3169(define query fluent API), ISPN-3173(add a new query operation over hotrod) and ISPN-3174(String-based query language) in place, this is about connecting the dots: invoke the remote query on the server and present the result to the user. > h3.On the client side > As described in ISPN-3173, the query is sent as a byte[] to the server: the payload. > The request payload is query specific (not defined in the HR protocol) and at this stage has the following format: [Q_TYPE] [QUERY_ST] [FIRST_INDEX] [PAGE_SIZE]. This format accommodates the remote query requirements as defined in ISPN-3169. > - Q_TYPE (protobuf's byte) and query identifier, 1 for JPAQL (this is the query type we'll support). In future we'll add different query types as well. > - QUERY_STRING (protobuf's string)- JPAQL string generated by the fluent API (ISPN-3169). Parameters are encoded in this string (vs being sent separately) > - FIRST_INDEX + PAGE_SIZE (protobuf's int)- used for paginating/iterating over the result set. > HR response: [HR_SUCESS_FLAG] [payload] > PAYLOAD = [NUM_EL] [PROJ_SIZE] [ELEMENTS] > - even though at this stage we don't support projections (see ISPN-3169) PROJ_SIZE is added for future compatibility when projection will be supported. > Note that the payload for both request and response should be marshalled with protobuf as this information is read/written over multiple clients. > h3.On the server side > - the server module reads the query operation and the payload (byte[]) > - invokes QueryFacade.query(byte[]) : byte[] > - QueryFacade is an interface defined in the server modules > - has an implementation in the remote-query module (new modules) > - the reason for adding this module: RemoteQueryImpl cannot be in the server modules (ASL) as it has a dependency on the query module (LGPL) which would "contaminate" the server module. Another option would be to merge it in the query module itself, but doesn't feel like a natural fit as its responsibility is serializing data (protobuf). OTOH if it is small we can merge it there so that we don't add a new module to the system? > > For an overview on the remote querying see https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2819) REST server ignores client header Accept-Charset

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2819?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2819: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > REST server ignores client header Accept-Charset > ------------------------------------------------ > > Key: ISPN-2819 > URL: https://issues.jboss.org/browse/ISPN-2819 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Affects Versions: 5.2.1.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Priority: Minor > > In a HTTP GET request, the client can specify an {{Accept-Charset}} header. The REST server will ignore it, and it will always send the response with the original PUT/POST request's charset. > I think the server should make an effort to transform the value data from the PUT charset to the GET charset. At the moment we don't even parse the PUT charset, we just store the {{Content-Type}} header. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3172) Define and manage indexes and schemas via JMX

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3172?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3172: -------------------------------- Priority: Blocker (was: Major) > Define and manage indexes and schemas via JMX > --------------------------------------------- > > Key: ISPN-3172 > URL: https://issues.jboss.org/browse/ISPN-3172 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Blocker > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > - ability to upload/attach a .proto file > - ability to edit indexing metadata, which maps to Hibernate Search programmatic metadata API > - store schema and metadata info in Metadata Store > For an overview on the remote query design refer to: https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3169) Define a Query API that will be common for library mode + remote

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3169?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3169: -------------------------------- Fix Version/s: 6.0.0.Alpha2 6.0.0.Final > Define a Query API that will be common for library mode + remote > ---------------------------------------------------------------- > > Key: ISPN-3169 > URL: https://issues.jboss.org/browse/ISPN-3169 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Some notes on the query API: > - fluent, supporting a predefined set of filters (equality, range, etc). No user pluggable filter will be supported as this API will be available both embedded and *remotely* by the Java HR client > - the filters accept the schema(protobuf) primitive types as arguments (int, string, byte, etc..) > - should support paging: start page + pageSize > - projections are not supported > For an overview on the remote query design refer to: https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3170) create a Metadata store

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3170?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3170: -------------------------------- Fix Version/s: 6.0.0.Alpha1 6.0.0.Final > create a Metadata store > ----------------------- > > Key: ISPN-3170 > URL: https://issues.jboss.org/browse/ISPN-3170 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > See #3: https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3170) create a Metadata store

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3170?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3170: -------------------------------- Labels: jdg62 (was: ) > create a Metadata store > ----------------------- > > Key: ISPN-3170 > URL: https://issues.jboss.org/browse/ISPN-3170 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: jdg62 > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > See #3: https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3172) Define and manage indexes and schemas via JMX

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3172?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3172: -------------------------------- Fix Version/s: 6.0.0.Alpha2 6.0.0.Final > Define and manage indexes and schemas via JMX > --------------------------------------------- > > Key: ISPN-3172 > URL: https://issues.jboss.org/browse/ISPN-3172 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > - ability to upload/attach a .proto file > - ability to edit indexing metadata, which maps to Hibernate Search programmatic metadata API > - store schema and metadata info in Metadata Store > For an overview on the remote query design refer to: https://community.jboss.org/wiki/QueryingDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013