id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
117 | XD-302 | 06/24/2013 14:06:17 | User wants ability to create a mock source | To send a pre-set message to process(es) | 8 |
118 | XD-303 | 06/24/2013 14:08:03 | User wants ability to create a in-process sink or tap | So that we can validate the message content in the stream | 8 |
119 | XD-304 | 06/24/2013 14:09:14 | User wants ability to test processors | Be able to point to the processor xml file, e.g. modules/processors/transformer.xml, and have access to a source channel that drives messages into the processor and a output channel where output messages are send. The outbound channel is queue backed. Test sending JSON to a processor module that uses Tuples. | 8 |
120 | XD-305 | 06/24/2013 14:09:58 | User wants ability to test sinks | Handled by 1245 | 8 |
121 | XD-306 | 06/24/2013 14:10:49 | User wants ability to test sources | Examples: 1. Be able to start the rabbitmq source just by pointing to modules/source/rabbit.xml, pass in some property file for parameters to be replaced, and outgoing message is placed in a in-memory queue backed channel for use with assertions to verify functionality. 2. Test for as many source types as is 'reasonable', e.g. MQTT/TCP testing might be harder than say rabbitmq. 3. Test that sending json, results in media-type header is set to json 4. Test that sending POJO, " POJO 5. Test that sending Tuple, " Tuple 6. Test that sending raw bytes, " raw bytes | 8 |
122 | XD-315 | 06/25/2013 07:41:05 | Package Shell "binary" next to xd-admin and xd-container | The shell should be an 'executable' delivered out of the box in much the same way that xd-container and xd-admin are right now. If we follow how redis/mongo distribut the shell, it sits side by side with the other binaries | 3 |
123 | XD-316 | 06/25/2013 08:30:23 | Create a common exception framework for XD | Need to capture exceptions from the various projects that make up XD and wrap them in XD Specific exceptions. An example of this is when leaving out the channels in the module definitions, we see NoSuchBeanExceptions and IllegalArgumentExceptions thrown based on which module and what channel is missing. | 5 |
124 | XD-340 | 06/26/2013 14:21:29 | Create script to extract table data from JSON based on a given HAWQ table structure | We should be able to write a script that can examine the table structure for a given HAWQ table and then extract the data from JSON without the custom script we are using now. | 8 |
125 | XD-341 | 06/27/2013 08:14:03 | Document JMX features | Document jmx command line options and refer to jolokia | 2 |
126 | XD-342 | 06/27/2013 13:50:13 | Fix classpath error caused by multiple conflicting servlet-api jars | There is some conflicting Servlet API jars on the claspath that needs cleanup. Building and running with xd-singlenode script gave this error: Jun 27, 2013 3:18:16 PM org.apache.coyote.http11.AbstractHttp11Processor process SEVERE: Error processing request java.lang.NoSuchMethodError: javax.servlet.ServletContext.getEffectiveSessionTrackingModes()Ljava/util/Set; at org.apache.catalina.connector.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:674) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) | 3 |
127 | XD-343 | 06/28/2013 07:34:54 | Investigate JMX object naming of deployed modules and inbound/outbound channel adapters. | The object naming is still not ideal for XD since SI conventions add some noise. Likely need to design and implement a custom naming strategy | 5 |
128 | XD-347 | 07/01/2013 03:53:10 | Investigate Redis connection timeout issues when running performance test | With the performance test run, the numbers (messages sent/received per second) keep varying as there are "redis client connection timeout exceptions" (Caused by: org.jboss.netty.channel.ConnectTimeoutException: connection timed out) at both redis inbound/outbound channel adapters as I increase the total number of messages being processed (max. 10K/second). Some of the exception messages for the review: 1) With connection pool (at Redis outbound): Caused by: org.springframework.data.redis.connection.PoolException: Could not get a resource from the pool; nested exception is com.lambdaworks.redis.RedisException: Unable to connect at org.springframework.data.redis.connection.lettuce.DefaultLettucePool.getResource(DefaultLettucePool.java:95) at org.springframework.data.redis.connection.lettuce.DefaultLettucePool.getResource(DefaultLettucePool.java:36) at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.createLettuceConnector(LettuceConnectionFactory.java:318) at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.getConnection(LettuceConnectionFactory.java:109) at org.springframework.data.redis.core.RedisConnectionUtils.doGetConnection(RedisConnectionUtils.java:81) at org.springframework.data.redis.core.RedisConnectionUtils.getConnection(RedisConnectionUtils.java:53) at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:157) at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:137) at org.springframework.data.redis.core.AbstractOperations.execute(AbstractOperations.java:84) at org.springframework.data.redis.core.DefaultListOperations.leftPush(DefaultListOperations.java:71) at org.springframework.data.redis.core.DefaultBoundListOperations.leftPush(DefaultBoundListOperations.java:67) at org.springframework.xd.perftest.redis.outbound.RedisQOutboundChannelAdapter.handleMessageInternal(RedisQOutboundChannelAdapter.java:71) at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:73) ... 17 more Caused by: com.lambdaworks.redis.RedisException: Unable to connect at com.lambdaworks.redis.RedisClient.connect(RedisClient.java:176) at com.lambdaworks.redis.RedisClient.connectAsync(RedisClient.java:139) at org.springframework.data.redis.connection.lettuce.DefaultLettucePool$LettuceFactory.makeObject(DefaultLettucePool.java:252) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1181) at org.springframework.data.redis.connection.lettuce.DefaultLettucePool.getResource(DefaultLettucePool.java:93) ... 29 more Caused by: org.jboss.netty.channel.ConnectTimeoutException: connection timed out: localhost/127.0.0.1:6379 at org.jboss.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137) at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) 2) Without connection pool (at Redis inbound): Caused by: com.lambdaworks.redis.RedisException: Unable to connect at com.lambdaworks.redis.RedisClient.connect(RedisClient.java:176) at com.lambdaworks.redis.RedisClient.connectAsync(RedisClient.java:139) at org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory.createLettuceConnector(LettuceConnectionFactory.java:321) ... 12 more Caused by: org.jboss.netty.channel.ConnectTimeoutException: connection timed out: localhost/127.0.0.1:6379 at org.jboss.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137) at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) ... 3 more | 2 |
129 | XD-348 | 07/01/2013 08:22:24 | Trigger - Add support for fixed-delay interval | Trigger - Add support for fixed-delay interval | 1 |
130 | XD-368 | 07/03/2013 11:11:27 | Improve connection handling in RedisAggregateCounterService. | This is currently too chatty. It should be possible to use a single connection for each "increment" operation. | 2 |
131 | XD-396 | 07/08/2013 09:49:24 | Add section to documentation that shows command line options available for each server | This should likely be in the "start the runtime" section of Getting Started section. | 1 |
132 | XD-397 | 07/08/2013 09:52:18 | Document Monitoring & Management Features | This section should discuss what is exposed via JMX, how you can view it in JConsole, and how you can view it over http via Jolikia. in particular showing how some existing metrics for inbound message channel adapters or the 'inbound' channel of the stream, that indicate the number of messages processed per section. | 2 |
133 | XD-398 | 07/08/2013 09:53:45 | Update Getting Started chapter to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#getting-started | 1 |
134 | XD-399 | 07/08/2013 09:54:28 | Update Getting Started chapter to include a section on starting the shell. | The chapter on how to start up the shell should ocme right after "start the runtime" and before "create the stream" | 1 |
135 | XD-400 | 07/08/2013 10:00:53 | Update Streams Chapter to use shell commands instead of curl | the current streams chapter http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#streams shows creation and deleting streams using CURL - switch to use shell. Also add listing of a stream. there is also an example of creating a stream, this should be replaced as well. | 1 |
136 | XD-401 | 07/08/2013 10:02:43 | Create a shell command to post data to an http port for use with the http source module | the current streams chapter http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#streams shows using curl to post some data to a http source module, curl -d "hello" http://localhost:9000 create a shell command so curl doesn't have to be used. https://github.com/SpringSource/rest-shell has a command already developed for this. | 1 |
137 | XD-403 | 07/08/2013 16:28:33 | Update Sources section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#http | 1 |
138 | XD-404 | 07/08/2013 16:36:08 | Update documentation section "Running in Distributed Mode" to show use of RabbitMQ in addition to Redis | The documentation in the Running in Distributed Mode chapter should discuss that the distributed runtime can use essentially any middleware to communicate between nodes. This functionality is provided by the core ChannelRegistry abstraction. A new intro paragraph shoul convey that it isn't a 'redis' only or 'rabbitmq' only system. There should be "Installing RabbitMQ" and "Starting RabbitMQ" sections to match those for Redis. "Starting Spring XD in Distributed Mode" should cover how to configure the system to select to use Redis or Rabbit. | 3 |
139 | XD-405 | 07/08/2013 17:14:39 | Update Sources tail section to use Shell commands instead of curl | http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#tail | 1 |
140 | XD-406 | 07/08/2013 17:15:16 | Update Sources twitter search section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#twittersearch | 1 |
141 | XD-407 | 07/08/2013 17:16:12 | Update Sources Gemfire CQ section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#gemfire-cq | 1 |
142 | XD-408 | 07/08/2013 17:16:43 | Update Source Syslog section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#syslog | 1 |
143 | XD-409 | 07/08/2013 17:17:49 | Update Sources TCP section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#tcp | 1 |
144 | XD-410 | 07/08/2013 17:27:35 | Update Processors Filter & JSon Filed Value Filter section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#filter http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#json-value-filter | 1 |
145 | XD-411 | 07/08/2013 17:28:44 | Update Processors Transform section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#transform | 1 |
146 | XD-412 | 07/08/2013 17:29:33 | Update Processors JSON Field Extractor section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#json-field-extractor | 1 |
147 | XD-413 | 07/08/2013 17:30:05 | Update Processors Script section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#script | 1 |
148 | XD-414 | 07/08/2013 17:31:49 | Update Sink's Log section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#log_sinks | 1 |
149 | XD-415 | 07/08/2013 17:32:27 | Update Sink's File section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#file_sinks | 1 |
150 | XD-416 | 07/08/2013 17:33:30 | Update Sink's HDFS section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#hdfs | 1 |
151 | XD-417 | 07/08/2013 17:34:20 | Update Sink's TCP section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#tcp_sinks | 1 |
152 | XD-418 | 07/08/2013 17:34:56 | Update Sink's GemFire section to use Shell commands instead of curl | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#gemfire | 1 |
153 | XD-419 | 07/08/2013 17:38:57 | Taps introduction section should show use of shell to create a real stream and a real tap using the shell | See http://static.springsource.org/spring-xd/docs/1.0.0.M1/reference/html/#taps The existing docs should be made to show a real stream being created with filter and/or transformer and then a tap that goes to logging. The shell syntax to also stop/undeploy a tap should be shown here as well since the lifecycle is discussed. | 2 |
154 | XD-429 | 07/09/2013 00:06:10 | Document time source | time source is used in some examples, but it isn't documented explicitly, eg. --interval option in seconds. | 1 |
155 | XD-432 | 07/09/2013 11:05:15 | User wants to configure MessageBus | XD-162 requires registering message converters with the ChannelRegistry. End user needs to configure this statically as the Spring configuration is not exposed. | 0 |
156 | XD-433 | 07/09/2013 11:40:19 | Homogenize Container Initialization Failures | If Redis is not running, the container fails to initialize in {{ContainerMain.launch()}} because the connection factory attempts to eagerly connect. If RabbitMQ is not running, the container fails to initialize in {{AbstractContainerLauncher.launch()}}. Make the failure behavior consistent from a user perspective and add a spring-retry {{RetryTemplate}} to retry container startup. | 5 |
157 | XD-434 | 07/09/2013 11:42:15 | Consider removing the Topic/Queues when deleting the Stream | As a user, I'd like to have the option to delete the queues/topics so that we can include an _optional_ attribute as part of the stream destroy command to also clean-up the associated queues/topics. *Notes:* * Spring-AMQP {{RabbitAdmin}} now has a {{getQueueProperties()}} method which returns the number of consumers so it may be possible to use it for this purpose. * Consider the possibility of _producers_ and/or _queues_ still containing data * Consider the scenario even after the topics/queues are cleaned-up, what to do with fanout exchange? *Some Further Thoughts* * Consider using the upcoming Spring AMQP REST API {{RabbitManagementTemplate}} if the timing is not right, we could temporarily invoke the rabbit REST API directly. * Should be optional; perhaps via {{stream destroy foo --clean}} * Should this be done by the admin? Or, via a new plugin handling module undeployments - in the rabbit case, undeploying a consumer would check for us being the last consumer and remove the queue/binding/exchange, since we undeploy left->right, everything can be cleaned up on the consumer side. * Third option would be new methods on the bus {{cleanConsumer}} etc invoked by the {{StreamPlugin}} * Down side of doing it on the admin is that he wouldn't necessarily know which rabbit cluster a stream was deployed to - so it probably has to happen on the container - even so, we'd need the admin url(s) for the cluster. | 5 |
158 | XD-436 | 07/10/2013 07:23:03 | Decouple transport from DIRT | Currently spring-xd-dirt has direct dependencies on Redis and Rabbit. Consider moving transport dependent classes to separate jars with "runtime" dependencies | 0 |
159 | XD-445 | 07/10/2013 18:04:11 | Add support to set the read timeout for http request | We need to have the ability to set read timeout for http request. This is already implemented here: https://github.com/SpringSource/rest-shell/ | 1 |
160 | XD-449 | 07/11/2013 15:26:53 | The user needs the ability to set up a misfire policy for a Trigger | 2 options are: 1) Fire the trigger immediate - Launch the job when trigger can gather the resources necessary start the job 2) Do nothing - Ignore this job fire time and catch this scenario can occur if XD is down or resources (threads) are not available at the time a job is to be launched. | 1 |
161 | XD-469 | 07/12/2013 11:54:27 | Upgrade to spring-data-hadoop 1.0.1.RC1 | spring-data-hadoop 1.0.1.RC1 provides flavors for commonly used Hadoop distros/versions and we should make use of that. | 1 |
162 | XD-470 | 07/12/2013 11:55:37 | Create JDBC sink | we need a JDBC sink for writing to HAWQ (using int-jdbc:outbound-channel-adapter and postgresql JDBC driver) | 3 |
163 | XD-471 | 07/12/2013 11:57:37 | Batching JDBC channel adapter | we need a batching JDBC channel adapter (int-jdbc:outbound-channel-adapter is not batching statements AFAICT) | 8 |
164 | XD-472 | 07/12/2013 11:58:59 | Add spring-xd-hadoop distro specific sub-projects | we need to modify build adding two sub-projects for spring-xd-hadoop: one for hadoop 1.1.2 and one for phd1 (Pivotal HD) to pull in transitive dependencies for correct Hadoop distro | 8 |
165 | XD-473 | 07/12/2013 12:01:25 | Modify startup script of xdadmin/xdcontainer to allow specifying hadoop distro to use | we need to modify startup script to use hadoop 1.1.2 as default or phd1 when specified with --hadoopDistro=phd1 | 5 |
166 | XD-474 | 07/12/2013 12:09:31 | Create JSON to tab-delimited text transformer script | We need a generic script that can do JSON to tab-delimited text transformation for data written to HDFS/HAWQ external tables. Users should be able to specify columns/fields to be included. | 8 |
167 | XD-475 | 07/12/2013 12:14:54 | Avro sink for HDFS | We need a sink that can write data in Avro serialized format. This story is for investigating what we would need to do to support that. The Spring Integration Kafka adapter provides Avro support for Kafka. | 8 |
168 | XD-478 | 07/15/2013 05:35:17 | Add accepted type logic to module | A module can declare one ore more payload types it will accept. This will inform the runtime re. automatic payload conversion. This can be done in the module XML configuration and processed by StreamPlugin | 3 |
169 | XD-479 | 07/15/2013 05:45:57 | Add conversion support to ChannelRegistrar and ChannelRegistry | Implements automatic conversion. Provide APIs to channel registry to register Payload conversion. Includes Redis and Rabbit transport. | 8 |
170 | XD-480 | 07/15/2013 07:10:45 | In certain scenarios a job can be redeployed more than once | In a scenario where we are using the same job definition i.e. Job.xml and we create Job Instance Foo. If I create and deploy Foo2 using Job.xml I will see only 2 job definitions(correct), but I will see the job run 3 times. If I create Foo3 & deploy, I will see 3 job definitions(correct), but the jobs will run 5 times. | 2 |
171 | XD-485 | 07/15/2013 09:34:36 | Create stories to enable the use of Spring Shell's 2.0 branch testing facilities | We need a few steps 1. Investigate if we need to move off Spring Shell 1.0 dependency, e.g. need to use code in Spring Shell 2.0 branch 2. If we need to use code in Spring Shell 2.0 branch, we need to release a Spring Shell 1.1 M1 release with appropriate code changes. Create stories related to Shell release. 3. Determine and document the basic recipe for doing integration tests. 4. Create stories to provide integration tests for each existing command | 5 |
172 | XD-496 | 07/15/2013 11:50:59 | Disable Collection to Object conversion in DefaultTuple | DefaultFormattingConversionService provides Collection -> Object conversion which will produce the first item if the target type matches. Here, this results in an unfortunate side effect, getTuple(List<Tuple> list) would return a Tuple which is misleading. In this case it is preferable to treat it as an error if the argument is not a Tuple. | 3 |
173 | XD-504 | 07/17/2013 12:14:23 | Add "How to Build Spring-XD" instructions to the documentation | We need to determine where this information could fit in. It can be either in "README" at the project home page or "Getting started" wiki page. | 1 |
174 | XD-514 | 07/18/2013 13:40:10 | Create proper test coverage for Controllers | Create proper test coverage for Controllers | 8 |
175 | XD-522 | 07/19/2013 21:31:48 | Cannot create tap if you have already tried to create an invalid one of same name | From the shell: {code} > stream create --name aaa --definition "time|log" Created new stream 'aaa' > tap create --name aa --definition "tap aaa | log" Command failed org.springframework.xd.rest.client.impl.SpringXDException: XD111E:(pos 8): Unexpected token. Expected 'dot(.)' but was 'pipe(|)' tap aaa | log >tap create --name aa --definition "tap aaa . log" Command failed org.springframework.xd.rest.client.impl.SpringXDException: There is already a tap named 'aa' {code} Looks like the first tap was created even though there was a parse error. And so the second attempt to create the tap failed due to an existing tap. | 1 |
176 | XD-540 | 07/24/2013 11:48:47 | Broadcast Undeploy Requests | Use an 'undeploy' topic to broadcast undeploy requests to all containers. Applies to Redis and Rabbit transports, not local. Also, rename {{ModuleDeploymentRequest}} to {{ModuleOperationRequest}} with an enum {{DEPLOY}}, {{UNDEPLOY}}. | 5 |
177 | XD-583 | 07/30/2013 09:38:18 | Dispatcher Has No Subscriber Error when posting a message to a stream | This has been observed intermittently with Redis transport by myself and others when sending a message to a valid stream. Not sure how to recreate it yet. 11:27:10,082 ERROR ThreadPoolTaskScheduler-1 redis.RedisQueueInboundChannelAdapter:126 - Error sending message org.springframework.integration.MessageDeliveryException: Dispatcher has no subscribers for channel 'org.springframework.context.support.GenericApplicationContext@3f73865d.input'. | 5 |
178 | XD-584 | 07/30/2013 09:49:20 | Parsing stream definition with parameter containing single quotes not working | The documented gemfire-cq example (https://github.com/springsource/spring-xd/wiki/Sources#wiki-gemfire-cq) fails: xd:>stream create --name cqtest --definition "gemfire-cq --query="Select * from /Stocks where symbol= 'VMW'" | file" You cannot specify option 'name' when you have also specified '' in the same command xd:>stream create --name cqtest --definition "gemfire-cq --query=Select * from /Stocks where symbol=' VMW' | file" 10:01:46,249 WARN Spring Shell client.RestTemplate:524 - POST request for "http://localhost:8080/str eams" resulted in 400 (Bad Request); invoking error handler Command failed org.springframework.xd.rest.client.impl.SpringXDException: XD115E:(pos 26): unexpected data in stream definition '*' gemfire-cq --query=Select * from /Stocks where symbol='VMW' | file ^ | 0 |
179 | XD-585 | 07/30/2013 10:28:55 | Deploying with twittersearch source throws Jackson ClassDefNotFound exception | The upgrade to Jackson 2.2 included the following change to the build script {code} project('spring-xd-dirt') { description = 'Spring XD DIRT' configurations { [runtime,testRuntime]*.exclude group: 'org.codehaus.jackson' } {code} Spring social twitter template depends on these classes | 1 |
180 | XD-592 | 08/01/2013 12:44:17 | Problems with advanced tapping | Start of a test program that can be placed in StreamCommandTests: {code} @Test public void testTappingAndChannels() { executeStreamCreate("myhttp","http --port=9314 | transform --expression=payload.toUpperCase() | log",true); executeStreamCreate("tap","tap @myhttp.1 | log",true); executeStreamCreate("tap_new","tap myhttp.1 > log",true); executeCommand("http post --data Dracarys! --target http://localhost:9314"); // TODO verify both logs output DRACARYS! } {code} In the test program see two taps. One using the older style and one using the newer style and '>' so that there is no real tap module source, the log module just gets its input channel wired directly to myhttp.1 (the output of transform). They should be doing the same thing. However when run the output for tap_new is missing, all I see is: {code} 11:39:36,055 WARN New I/O worker #28 logger.tap:141 - DRACARYS! 11:39:36,059 WARN New I/O worker #28 logger.myhttp:141 - DRACARYS! {code} No errors are reported, there is just no output for tap_new. | 8 |
181 | XD-593 | 08/02/2013 08:44:21 | Add "counter delete" shell command | Add "counter delete" shell command. This also requires implementation of DELETE rest end point at CountersController. | 1 |
182 | XD-594 | 08/02/2013 10:54:56 | Create list/delete commands for all the metrics | We need to add list/delete commands for the metrics: InMemoryAggregateCounter FieldValueCounter Gauge RichGauge Currently, the AbstractMetricsController class has the delete method to delete the metric from the repository. We can probably use the same for all the metrics. | 2 |
183 | XD-595 | 08/02/2013 11:11:46 | Fix wiki documentation to use xd shell command prompt to read "xd:>" | We need to fix the github wiki to use the xd shell command prompt "xd:>". | 1 |
184 | XD-596 | 08/02/2013 12:01:57 | Add CONTRIBUTING.md file | Add CONTRIBUTING.md file, use the Spring Integration file as the basis. | 1 |
185 | XD-613 | 08/06/2013 11:14:09 | Deployed streams should be restarted on container start | When using Redis store, stored deployed streams should be deployed on container restart. | 5 |
186 | XD-614 | 08/06/2013 12:14:44 | Conversion Enhancements | Content-Type during transport transit is not the same as the content-type within modules. "Real" transports always use byte[] which may contain raw byte[] from a source, a byte[] converted from a String (which may or may not already contain JSON), or a byte[] containing JSON converted by the transport on the outbound side. The transport needs to convey which of these was applied on the outbound side so it can properly reconstruct the message. Retain any content-type header that already exists in the message, and restore it. For Rabbit, use normal SI/Rabbit headers to convey this information. For Redis, add the information to the byte[]. | 8 |
187 | XD-621 | 08/07/2013 08:30:14 | Set Default Hadoop Name Node for Shell | Currently, you have to set the default name node every time your start the shell. We should do 2 things: - Provide a default Name node Set Default Hadoop Name Node for Shell: hdfs://localhost:8020 - Should we provide some form of persistence? It kind of sucks that you have to re-specify the name node every time the shell starts up {code} xd:>hadoop fs ls / You must set fs URL before run fs commands {code} | 2 |
188 | XD-624 | 08/07/2013 11:58:16 | Use External Connection Factory in TCP Syslog Source | WARN log emitted because the embedded connection factory does not get an application event publisher. Will be fixed in SI M3 (INT-3107). | 1 |
189 | XD-631 | 08/08/2013 07:17:54 | Pluralize test classes in package org.springframework.xd.shell.command | The classes under test are pluralized. Therefore, the test classes themselves should reflect that. E.g. rename *JobCommandTests* to *JobCommandsTests* as it tests class *JobCommands*. Please check all tests in that package for correct naming. | 1 |
190 | XD-634 | 08/08/2013 09:34:46 | Fix guava dependency for hadoop20 and phd1 | Spring Xd currently ships with Guava 12.0 while Hadoop 2.0.5 and Pivotal HD 1.0 depends on 11.0.2 - this could lead to classpath problems if we include both. | 3 |
191 | XD-640 | 08/08/2013 15:12:17 | Cannot start xd-container with the --hadoopDistro option | Trying to use xd-container with PHD, and therefore need to start with --hadoopDistro. I get the following error: $ bin/xd-container --hadoopDistro phd1 17:11:20,305 ERROR main server.ContainerMain:59 - "--hadoopDistro" is not a valid option | 3 |
192 | XD-643 | 08/08/2013 17:03:17 | Map column names with underscore to camelCase style keys for JDBC sink | We need to add support for matching column names with underscores like "user_name" and map them to camel case style keys like "userName" in the JdbcMessagePayloadTransformer. | 3 |
193 | XD-650 | 08/09/2013 09:48:15 | Eclipse build path error after running gradle -> refresh source folders in Eclipse | After running gradle -> refresh source folders on the spring-xd-module project in Eclipse, there is an error because the {{src/test/java}} folder is missing. Solution is to add a placeholder file. | 5 |
194 | XD-654 | 08/09/2013 12:10:26 | Support explict named channel creation with configurable settings via the REST API and Shell | Support pubsub named channels… the story could be a bit more general though: enable channel creation (with configurable settings) via the REST API and shell >namedchannel create foo --domain PUBSUB | 0 |
195 | XD-658 | 08/09/2013 13:36:44 | Update to Spring-Data-Redis 1.1.0.M2 | Remove the {{NoOpRedisSerializer}} and use the non-serialization feature of M2. | 2 |
196 | XD-663 | 08/09/2013 16:59:59 | Use correct FS_DEFAULT_NAME_KEY constant based on Hadoop version used | Keep getting the following warning: WARN Spring Shell conf.Configuration:817 - fs.default.name is deprecated. Instead, use fs.defaultFS Should switch to use the runtime value of the FS_DEFAULT_NAME_KEY constant based on Hadoop version used. | 3 |
197 | XD-665 | 08/09/2013 18:13:03 | AggregateCounter display command options with "lastHours" and "lastDays" | It would be nice to have "lastHours" and "lastDays" options for aggregatecounter display command. | 1 |
198 | XD-686 | 08/12/2013 16:24:33 | Support Named Taps (or Similar) | Provide some syntax allowing multiple tap points to be directed to a named channel. e.g. tap foo.4 > namedTap tap bar.2 > namedTap or :tap.foo > counter | 8 |
199 | XD-699 | 08/14/2013 17:14:00 | Handling tap operations on a tap that has reference to a deleted stream | When trying to undeploy/destroy a tap that has reference to an already deleted stream fails with the following exception: Command failed org.springframework.xd.rest.client.impl.SpringXDException: XD116E:(pos 4): unrecognized stream reference '<stream_name at the tap defintion>'. As expected, the StreamConfigParser's lookupStream fails to find the stream name as the stream doesn't exist in the repository. In this scenario, what is a better way to handle the tap operations. Should we undeploy the tap when the stream is destroyed? ( though I don't see an easy way to find the taps that use a specific stream). | 2 |
200 | XD-724 | 08/20/2013 11:52:52 | Test source module in isolation | Register the module under test and deploy the module Verify output across all transports Examples Be able to start the rabbitmq source just by pointing to modules/source/rabbit.xml, pass in some property file for parameters to be replaced, and outgoing message is placed in a in-memory queue backed channel for use with assertions to verify functionality. Test that sending json, results in media-type header is set to json Test that sending POJO -> POJO Test that sending Tuple -> Tuple Test that sending a (JSON) String -> String Test that sending raw bytes -> raw bytes | 5 |
201 | XD-725 | 08/20/2013 11:54:20 | Test processor module in isolation | Register the module under test and have access to a source channel that drives messages into the processor and a output channel where output messages are sent. Examples Built-in Message conversion: send JSON to a processor module that accepts Tuples. | 5 |
202 | XD-726 | 08/20/2013 11:54:52 | Test sink module in isolation | Register the module under test Send a message to the sink using a test source and verify the sink contents - this requires checking an external resource - depends on the sink | 5 |
203 | XD-747 | 08/23/2013 06:31:10 | Bootstrap XD on Yarn | 1. How XD Yarn application should be packaged and bootstrapped? 2. Where the code should be? Within xd itself or separate repo? | 1 |
204 | XD-748 | 08/23/2013 06:34:55 | Interacting with XD on Yarn | 1. How we talk to the XD instance(s) on Yarn 2. There is a rest interface which location can be exposed either via resource manager or appmaster 3. Technically appmaster could also expose interface which could eihter be proxy for xd rest or dedicated interface implementation(i.e. thrift or spring int) | 1 |
205 | XD-749 | 08/23/2013 06:38:07 | Comm protocol for appmaster | We need to be able to talk to appmaster which will control the whole xd yarn app. 1. Choose the implementation? Thrift? Spring Int? Something else? | 1 |
206 | XD-750 | 08/23/2013 06:41:25 | Container and Grid Control | 1. We'll need a system which give better control of what yarn/xd containers are out there and what is a status of those containers. 2. We also need grouping of containers order to choose, prioritize and scale tasks. 3. We need heartbeating of the grid nodes. Hadoop Yarn itself doesn't give enough tools to know if container is "alive". | 1 |
207 | XD-751 | 08/23/2013 06:53:08 | XD UI on Yarn | Technically speaking of we want to integrate XD UI on Hadoop tools we should do it so that the proxy on resource manager works with XD UI. From Hadoop Yarn resource manager point of view this proxied url is the applications tracking url(which is registered when application is deployed). | 1 |
208 | XD-752 | 08/23/2013 18:50:20 | Restrict Job launcher with more than one batch job configured in job module | Currently the Job launcher launches all the batch jobs configured in the job module. Please refer, ModuleJobLauncher's executeBatchJob(). This makes the JobRegistry registers with multiple batch jobs under the same Spring XD job name (group name). Also, it is understood that having multiple jobs configuration under the same config xml is uncommon. | 2 |
209 | XD-754 | 08/25/2013 07:57:35 | Fix Class/Package Tangle Introduced by XD-353 | {{container}} and {{event}}. {{XDContainer}} references and is referenced by {{ContainerStartedEvent}} (and stopped). https://sonar.springsource.org/drilldown/measures/7173?metric=package_cycles&rids%5B%5D=7717 | 1 |
210 | XD-755 | 08/26/2013 09:26:34 | Reactor Environment Improvements | Use a profile or similar to only include the {{Environment}} conditionally (currently in module-common.xml. Also Jon Brisbin one thing to keep in mind: we talked about having a properties file for XD that configured the RingBuffer et al in a non-default way Jon Brisbin e.g. no event loop Dispatchers…a ThreadPoolDispatcher with a large thread pool size (50 threads? 100?)…and maybe even two RingBufferDispatchers: input and output Jon Brisbin so we might want to change from strictly a default Environment bean to an EnvironmentFactoryBean with a specific configuration…thinking about it now I maybe should add a namespace element for the Environment | 3 |
211 | XD-773 | 08/28/2013 09:26:50 | Tab support inconsistent for http post | When doing *xd:> http post* and press the *tab* key. One should get a list of available options. Right now nothing happens. I have to press *--* and then tab to get the options. Interestingly, this works for *stream create* + *tab* key | 2 |
212 | XD-776 | 08/28/2013 15:46:41 | Shell: Remove "taps list" command | We should only allow "tap list" - currently "tap list" AND "taps list" are allowed but "tap list" does not show up under help. | 1 |
213 | XD-788 | 08/29/2013 11:22:21 | Add Integration Tests to run JobCommands Tests against all transports | similar to ChannelRegistry: - AbstractChannelRegistryTests that has the real tests - subclasses for each impl provide the registry to be tested Thus one test can run against multiple transports. | 8 |
214 | XD-804 | 09/04/2013 08:15:33 | Add Named Channel API | We need an abstraction in place to retrieve messages from a "named channel" programmatically. Right now there is no implementation agnostic way of doing this (such as receiveMessage(), queueSize()). This could be quite useful for integration tests of streams. E.g. to do more focussed tests without resorting to "temp-files" and non-essential sinks or sources etc. - e.g. {code} :routeit > router --expression=payload.contains('a')?':foo':':bar' {code} | 8 |
215 | XD-805 | 09/04/2013 08:18:41 | Get notified when created named channel "is ready" | For testing purposes it would be super-helpful if there be a hook to get notified when a named channel is up and running. In current tests one may have to resort to "Thread.sleep". | 8 |
216 | XD-807 | 09/04/2013 11:56:50 | Shell: Standardize counter name parameter | The parameters are not optimal for the counter name between "Aggregate Counter" "Field Value Counter" --counterName versus --name | 2 |
Subsets and Splits