profile
viewpoint

nats-io/spring-nats 18

A Spring Cloud Stream Binder for NATS

pivotal/java-functions 6

Stand alone Java functions.

pivotal/polyglot-pas-demo 2

Java and .Net - Better Together. How Spring Cloud Services and Steeltoe can help polyglot solutions work seamlessly together. First shown at MicroSoft Build 2019.

sabbyanandan/eda 2

SpringOne Platform 2018: Building Cloud-Native Data-Intensive Applications with Spring

pivotal-cf/service-instance-logs-cli-plugin 1

A Cloud Foundry CLI plugin for access service instance logs

sabbyanandan/combined-board 0

Combine spring-cloud-dataflow and the family in one board.

pull request commentspring-cloud-stream-app-starters/stream-applications

Handle byte array text payloads

Merged upstream.

tzolov

comment created time in a day

PR merged spring-cloud-stream-app-starters/stream-applications

Handle byte array text payloads
  • Leverage the app maven plugin's function composition and the ByteArrayTextToString function to covert byte array text to String

    • for log sink: functionDefinition = byteArrayTextToString|logConsumer
    • for counter sink: functionDefinition = byteArrayTextToString|counterConsumer
    • for filter processor: functionDefinition = byteArrayTextToString|filterFunction
    • for spel processor: functionDefinition = byteArrayTextToString|spelFunction
  • Add Counter analytics Sink & tests Related to https://github.com/spring-cloud-stream-app-starters/app-starters-release/issues/222 Depends on https://github.com/pivotal/java-functions/pull/17

  • Add Filter Processor & tests Leverage the existing FilterFunctionConfiguration in the java-function project.

Depends on: https://github.com/pivotal/java-functions/pull/21

+350 -6

0 comment

12 changed files

tzolov

pr closed time in a day

push eventspring-cloud-stream-app-starters/stream-applications

Christian Tzolov

commit sha 9fa3bd4ad6e6f71619df62aa6280e359bd031beb

Handle byte array text payloads - Leverage the app maven plugin's function composition and the ByteArrayTextToString function to covert byte array text to String - for log sink: functionDefinition = byteArrayTextToString|logConsumer - for counter sink: functionDefinition = byteArrayTextToString|counterConsumer - for filter processor: functionDefinition = byteArrayTextToString|filterFunction - for spel processor: functionDefinition = byteArrayTextToString|spelFunction - Add Counter analytics Sink & tests Related to https://github.com/spring-cloud-stream-app-starters/app-starters-release/issues/222 Depends on https://github.com/pivotal/java-functions/pull/17 - Add Filter Processor & tests Leverage the existing FilterFunctionConfiguration in the java-function project. Depends on: https://github.com/pivotal/java-functions/pull/21

view details

push time in a day

PR closed pivotal/java-functions

Consistent handling of byte array text input
  • Move the byte array text to String conversion logic into a standalone ByteArrayTextToString top-level function part of the payload-converter-function project.
  • Remove the byte array text to String conversion form the various supplier, function and consumer projects. Use function composition instead. e.g. byteArrayTextToString | logConsumer.
+218 -50

1 comment

12 changed files

tzolov

pr closed time in a day

pull request commentpivotal/java-functions

Consistent handling of byte array text input

Merged upstream.

tzolov

comment created time in a day

push eventpivotal/java-functions

Christian Tzolov

commit sha 3483af544e2efd29c39ea9fa5e25bebf02ffd0a7

Consistent handling of byte array text input - Move the byte array text to String conversion logic into a standalone ByteArrayTextToString top-level function which is part of the payload-converter-function project. - Remove the byte array text to String conversion form the various supplier, function and consumer projects. Use function composition instead. e.g. byteArrayTextToString | logConsumer.

view details

push time in a day

issue closedspring-cloud/spring-cloud-stream-binder-kafka

Map Kafka producer/consumer properties into Spring Cloud Stream properties automatically

As a user, I'd like to have my existing Kafka producer/consumer properties mapped into Spring Cloud Stream properties so that I don't have to explicitly specify spring cloud stream properties when using Apache Kafka as the binder.

For instance, the properties from https://kafka.apache.org/documentation/#configuration can be mapped into appropriate Spring Cloud Stream properties. This way, I don't have to maintain both the Apache Kafka as well as Spring Cloud Stream properties (wherever they are applicable).

closed time in 2 days

ilayaperumalg

issue closedspring-cloud/spring-cloud-stream-binder-kafka

Avoiding a rebalance if you need to wait longer than the heartbeat

Hi Folks, I have a problem that doesn't happen with spring-kafka and I would like to know if there is a right way to do with spring-cloud-stream-kafka.

The scenario: I have business logic to wait for some specific time duration to process the next message. The problem: Using the approach bellow, if the time is greater than 10sec, the kafka start rebalance given the heartbeat process.

    @Override
    public void run(ApplicationArguments args) {
        new Thread(() -> doWork(errors, events)).start();
    }

    private void doWork(PollableMessageSource source, MessageChannel output) {
        while(true) {
            try {
                source.poll(message -> errorProcessor.process(message, output),
                        new ParameterizedTypeReference<Event>() {});
                
                Thread.sleep(sleepTime);  ///// If this time is greater than 10 sec, the
            } catch (InterruptedException e) {
                log.error("Fail to sleep thread: {}", e.getMessage());
            }
        }
    }

My founds: Looks like given I'm waiting with Thread.sleep() the main thread is locked and this is why the heartbeat time out and then Kafka restart to rebalance. Make senses?

With this, I have tested the spring-kafka directly and with it works fine the code below:

    @KafkaListener(topics = "topic", groupId = "group1")
    public void consume(String message) {
        logger.info(String.format("#### -> Consumed message-> %s", message));
        try {
            Thread.sleep(60*1000);
        } catch (InterruptedException e) {
            e.printStackTrace();
        }

        logger.info("#### -> end waiting for...");
    }

I got this idea from this Github issue from spring-kafka and on the same page I could see the there was an implementation to do the heartbeat to Kafka in the background, so this is why I imagine works for that approach.

Do you know if there is somehow to do this same idea using spring-cloud-stream? or if something that is needed to implement it?

closed time in 2 days

samukce

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Avoiding a rebalance if you need to wait longer than the heartbeat

Closing this due to no recent activity.

samukce

comment created time in 2 days

issue closedspring-cloud/spring-cloud-stream-binder-kafka

KTable binding in Kafka Streams binder

When we do an inbound binding on KTable, currently the deserialization is done by the broker. As a developer, if I choose Spring Cloud Stream to do this deserialization it should be possible to do so.

closed time in 2 days

sobychacko

issue commentspring-cloud/spring-cloud-stream-binder-kafka

KTable binding in Kafka Streams binder

Starting from 3.0, we default to Kafka Streams provided native Serdes for de/serialization. There is still a way to use the framework serialization for KStream. We haven't encountered a need for providing the same for the table types. Closing the issue.

sobychacko

comment created time in 2 days

issue closedspring-cloud/spring-cloud-stream-binder-kafka

Resolve the Kafka Broker and zookeeper node from service discovery

Currently the kafka brokers and zoo keeper nodes are fetched from these properties spring.cloud.stream.kafka.binder.zkNodes= spring.cloud.stream.kafka.binder.brokers=

Can we have the feature where we instead of specifying the absolute broker and zknode values here , we just give the serviceName and get it discovered from the service discovery server like (Eureka or consul)

closed time in 2 days

Addymaddy

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Resolve the Kafka Broker and zookeeper node from service discovery

This issue is no longer a requirement and out of scope. Closing the issue.

Addymaddy

comment created time in 2 days

issue closedspring-cloud/spring-cloud-stream-binder-kafka

Refactor and adapt to core's error-handling strategy

As a developer, I'd like to refactor kafka-binder's error handling implementation to adapt to core's new abstraction.

This is a continuation of spring-cloud/spring-cloud-stream#1036, but the changes required in kafka-binder.

closed time in 2 days

sabbyanandan

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Refactor and adapt to core's error-handling strategy

This issue is no longer a requirement and out of scope. Closing the issue.

sabbyanandan

comment created time in 2 days

issue closedspring-cloud/spring-cloud-stream-binder-kafka

Make it possible to use a different ProducerFactory/ConsumerFactory from the KafkaMessageChannelBinder

Hi, I am trying to use a different implementation of the Kafka Consumer/Producer (https://github.com/linkedin/li-apache-kafka-clients/blob/master/src/main/java/com/linkedin/kafka/clients/producer/LiKafkaProducer.java / LiKafkaConsumer.java). For this I need KafkaMessageChannelBinder to be able to create those producer/consumer. Unfortunately KafkaMessageChannelBinder is hardcoded to return the Default factories:

private DefaultKafkaProducerFactory<byte[], byte[]> getProducerFactory(
		ExtendedProducerProperties<KafkaProducerProperties> producerProperties) {
	Map<String, Object> props = new HashMap<>();
	props.put(ProducerConfig.RETRIES_CONFIG, 0);
	props.put(ProducerConfig.BUFFER_MEMORY_CONFIG, 33554432);
	props.put(ProducerConfig.KEY_SERIALIZER_CLASS_CONFIG, ByteArraySerializer.class);
	props.put(ProducerConfig.VALUE_SERIALIZER_CLASS_CONFIG, ByteArraySerializer.class);
	props.put(ProducerConfig.ACKS_CONFIG, String.valueOf(this.configurationProperties.getRequiredAcks()));
	if (!ObjectUtils.isEmpty(configurationProperties.getConfiguration())) {
		props.putAll(configurationProperties.getConfiguration());
	}
	if (ObjectUtils.isEmpty(props.get(ProducerConfig.BOOTSTRAP_SERVERS_CONFIG))) {
		props.put(ProducerConfig.BOOTSTRAP_SERVERS_CONFIG, this.configurationProperties.getKafkaConnectionString());
	}
	if (ObjectUtils.isEmpty(props.get(ProducerConfig.BATCH_SIZE_CONFIG))) {
		props.put(ProducerConfig.BATCH_SIZE_CONFIG, String.valueOf(producerProperties.getExtension().getBufferSize()));
	}
	if (ObjectUtils.isEmpty(props.get(ProducerConfig.LINGER_MS_CONFIG))) {
		props.put(ProducerConfig.LINGER_MS_CONFIG, String.valueOf(producerProperties.getExtension().getBatchTimeout()));
	}
	if (ObjectUtils.isEmpty(props.get(ProducerConfig.COMPRESSION_TYPE_CONFIG))) {
		props.put(ProducerConfig.COMPRESSION_TYPE_CONFIG,
				producerProperties.getExtension().getCompressionType().toString());
	}
	if (!ObjectUtils.isEmpty(producerProperties.getExtension().getConfiguration())) {
		props.putAll(producerProperties.getExtension().getConfiguration());
	}
	return new DefaultKafkaProducerFactory<>(props);
}

closed time in 2 days

sebay

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Make it possible to use a different ProducerFactory/ConsumerFactory from the KafkaMessageChannelBinder

This issue is no longer a requirement and out of scope. Closing the issue due to inactivity.

sebay

comment created time in 2 days

issue closedspring-cloud/spring-cloud-stream-binder-kafka

Creating a DLQ fails if group name does not pass topic name validations

When the DLQ is created, the pattern to create the topic name is:

  • error.<destination>.<group>

The <group> part is refering to the current group name and this value is not validated with same rules as the topic name (using the org.springframework.cloud.stream.binder.kafka.KafkaTopicUtils#validateTopicName method)

So, if the group name contains special chars like ":" the dlq topic creation fails...

I would like to contribute to solve the problem, but I don't know what would be the better approach:

  1. Validate the group name with the KafkaTopicUtils class if the enableDlq option is enabled
  2. Filter the group name on the fly to create a valid DLQ topic name.

any suggestions?

closed time in 2 days

odin-delrio

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Creating a DLQ fails if group name does not pass topic name validations

This issue is no longer a requirement and out of scope. Closing the issue.

odin-delrio

comment created time in 2 days

issue closedspring-cloud/spring-cloud-stream-binder-kafka

Kafka Binder should support listening to specific partitions

To some extent, it is possible to do that today by setting the instanceCount and instanceId properly, but this should be made more intuitive for the end user.

closed time in 2 days

mbogoevici

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Kafka Binder should support listening to specific partitions

This issue is no longer a requirement and out of scope. Closing the issue.

mbogoevici

comment created time in 2 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Metric names are mutated/sanitized for Kafka Micrometer non-universally

@ctoestreich Any feedback that you want to provide based on what @tzolov commented above?

ctoestreich

comment created time in 3 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

bind different type of topics in the same broker not working

@AlvinYueChao We will keep this issue open for trying to come up with some alternatives in 3.1.

AlvinYueChao

comment created time in 3 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

bind different type of topics in the same broker not working

@AlvinYueChao We also came to sort of the same conclusion. The access credentials are set statically per classloader, thus the jaas configuration set through the second binder context is ignored. We cannot simply pass it along, as jaas won't allow resetting that. As you said, if they make it relaxed, then it will work, but I am not sure how feasible it is to address those issues at the core java security foundation. In fact, there might be valid reasons why it is designed that way.

We can potentially fix this in the binder by loading the binder contexts in separate classloaders. That will make sure that the second update is visible for the access controller. However, we won't be able to make such a major change in 3.0.x SR releases. It has to wait until the next major release 3.1, as this needs to be tested thoroughly for any side effects.

In the meantime, may I ask, why do you have separate access controls for the two topics? Are they on two different Kafka clusters? Or the same cluster, but different login credentials? If you can make the logins the same, that can be used as a workaround.

AlvinYueChao

comment created time in 3 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

bind different type of topics in the same broker not working

@AlvinYueChao I was able to reproduce your issue. I am still investigating to see if this is a bug in the binder. Basically, the second time a binder context is created (from the multi binder context), the jass properties specified in that context are not properly propagated to the jaas handler. I can see that the KafkaJaasLoginModuleInitializer bean is properly created from the multi binder context. I will try to debug more/discuss with the team internally and find out what the resolution is. Thanks for bringing this to our attention.

AlvinYueChao

comment created time in 3 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

bind different type of topics in the same broker not working

@AlvinYueChao I will run an application with your configuration and get back to you.

AlvinYueChao

comment created time in 3 days

IssuesEvent

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Possible conflict between Binder and Spring Kafka regarding enable.auto.commit

@garyrussell That sounds like a good idea to me. The binder property autoCommitOffset is always a source of confusion as it implies a Kafka property. We can deprecate that use ackMode as you suggested. Reopening the issue to track that. Thanks.

jskim1991

comment created time in 4 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

Overriding "(consumer|producer)Properties.bootstrap.servers" should be prohibited

@thspinto Based on the gitter chat, multi binders should solve your problem. Take a look at this configurationwhere it sets separate bootstrap configurations. Why did you reopen the issue? To address what Gary suggested?

thspinto

comment created time in 4 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

bind different type of topics in the same broker not working

@AlvinYueChao I am not sure what the issue is. From that zip file that you attached ^^, I see an exception - something as below.

org.springframework.cound.stream.binder.BinderException: Exception thrown while starting consumer: 
	at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:435)
    at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:97)
    at org.springframework.cloud.stream.binder.AbstractBinder.bindConsumer(AbstractBinder.java:142)
    at org.springframework.cloud.stream.binding.BindingService.doBindConsumer(BindingService.java:144)
    at org.springframework.cloud.stream.binding.BindingService.doBindConsumer(BindingService.java:122)
    at org.springframework.cloud.stream.binding.BindableProxyFactory.createAndBindInputs(BindableProxyFactory.java:254)
    at org.springframework.cloud.stream.binding.InputBindingLifecycle.doStartWithBindable(InputBindingLifecycle.java:58)
    at java.util.LindedHashMap$LinkedValues.forEach(LinkedHashMap.java:608)
    at org.springframework.cloud.stream.binding.AbstractBindingLifecycle.start(InputBindingLifecycle.java:48)
    ...
Caused by: java.lang.IllegalArguementException: A list of partitions must be privided 
	at org.springframework.util.Assert.isTrue(Assert.java:118)
	at org.springframework.cloud.stream.binder.kafka.KafkaMessageChannelBinder.createConsumerEndpoint(KafkaMessageChannelBinder.jave:432)
	at org.springframework.cloud.stream.binder.kafka.KafkaMessageChannelBinder.createConsumerEndpoint(KafkaMessageChannelBinder.jave:132)
	at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:382)
	... 24 common frames omitted

However, in your above analysis, you seem to imply that you are getting a SaslAuthenticationException. Please have a look at this configuration from our samples repository: https://github.com/spring-cloud/spring-cloud-stream-samples/blob/master/multi-binder-samples/kafka-multi-binder-jaas/src/main/resources/application.yml. That sample indeed takes jaas.options in the configuration. I suggest starting with that sample and compare notes with your configuration and see where it deviates from the sample.

Even after trying that sample, if you are still having trouble running it, could you provide a small standalone application for us to debug with instructions on how we can reproduce the issue?

AlvinYueChao

comment created time in 4 days

issue commentspring-cloud/spring-cloud-stream-binder-kafka

bind different type of topics in the same broker not working

@AlvinYueChao I will have a look at this today.

AlvinYueChao

comment created time in 5 days

push eventspring-cloud-stream-app-starters/stream-applications

Soby Chacko

commit sha 61df4e2078540f5f24893e9a14f8a73f935a7a84

Fix tests

view details

push time in 5 days

push eventspring-cloud-stream-app-starters/stream-applications

Soby Chacko

commit sha d85a8e6ae29712c89de6b23c45e59970fa878a5e

Restructuing app generation source/sink/processor as top level folders simpler structure for generating the apps Resolves https://github.com/spring-cloud-stream-app-starters/stream-applications/issues/4

view details

push time in 5 days

issue closedspring-cloud-stream-app-starters/stream-applications

Redesign the project structure

  • Create a top-level source, processor, and sink modules
  • Share the common parent project/module
  • We will adapt and follow the spring-boot starter model for the apps
  • We will always be able to deploy the app (as jar)

closed time in 5 days

sabbyanandan

push eventspring-cloud-stream-app-starters/jenkins-jobs

Soby Chacko

commit sha 4b2ddd49aacce94613a293cc30d7d93d6c9c33cb

Cleanup build steps

view details

push time in 5 days

push eventspring-io/dataflow.spring.io

Soby Chacko

commit sha 41907d7cc573287a2a4142e8c434e4f671670116

Update Einstein apps links Update Einstein apps redirect links from SR5 to SR6.

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/jenkins-jobs

Soby Chacko

commit sha 05cb346b4ce50926f6b99d218ddaa97e311f26ed

Einstein builds back to snapshot

view details

push time in 6 days

create barnchsobychacko/app-starters-release

branch : Einstein

created branch time in 6 days

push eventspring-cloud-stream-app-starters/app-starters-release

Soby Chacko

commit sha bddcd64197b9662b02f3c1f213dbf7a34eccd095

Next version: Einstein.BUILD-SNAPSHOT

view details

push time in 6 days

created tagspring-cloud-stream-app-starters/app-starters-release

tagvEinstein.SR6

Spring Cloud Stream App Starters and its Release Train

created time in 6 days

push eventspring-cloud-stream-app-starters/app-starters-release

Soby Chacko

commit sha 474f5de508d74324f7007323e3426f210b3180a1

Update copyrights to 2020

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/app-starters-release

Soby Chacko

commit sha 34c8db1912d2c3f1010a794e0322ef442f63f688

Fix cdc-debezium docs

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/app-starters-release

Soby Chacko

commit sha 94113b9cdd6811bd06eb12e49de35013e24147eb

Einstein.SR6

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/cdc-debezium

Soby Chacko

commit sha 0fcce79e4b2792cc12d5a4c4900939e9534dba0e

Next version: 1.0.2.BUILD-SNAPSHOT

view details

push time in 6 days

push eventsobychacko/cdc-debezium

Soby Chacko

commit sha 0fcce79e4b2792cc12d5a4c4900939e9534dba0e

Next version: 1.0.2.BUILD-SNAPSHOT

view details

push time in 6 days

created tagspring-cloud-stream-app-starters/cdc-debezium

tagv1.0.1.RELEASE

Change Data Capture (CDC) source that captures and streams change events from various databases. Leverages on Debezium and supports MySQL, PostgreSQL, MongoDB, Oracle and SQL Server databases.

created time in 6 days

push eventspring-cloud-stream-app-starters/cdc-debezium

Soby Chacko

commit sha c1a4052919217e0c2bc7a6f5879e471bef574510

1.0.1.RELEASE

view details

push time in 6 days

push eventsobychacko/cdc-debezium

Soby Chacko

commit sha abbf5d45719b302d33bb85fd6089f65438ca7f02

1.0.0.RELEASE

view details

Soby Chacko

commit sha 41a0d26ae412385db1810f262cf1fa73fb8b423f

Next version - 1.0.1.BUILD-SNAPSHOT

view details

Christian Tzolov

commit sha 4a75c0eca8c59350eb71ec20e067a3d309ef9e8a

Enable container image app metadata support

view details

Christian Tzolov

commit sha 491c544e4eb4360b0c3b6d03340e84fdf3fda819

Gracefully handle missing keys

view details

Soby Chacko

commit sha c1a4052919217e0c2bc7a6f5879e471bef574510

1.0.1.RELEASE

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/tasklauncher-dataflow

Soby Chacko

commit sha 0a291fa471ab77ca660be564d45456fc1c54fbea

Next version: 1.1.1.BUILD-SNAPSHOT

view details

push time in 6 days

push eventsobychacko/tasklauncher-dataflow

Soby Chacko

commit sha 0a291fa471ab77ca660be564d45456fc1c54fbea

Next version: 1.1.1.BUILD-SNAPSHOT

view details

push time in 6 days

created tagspring-cloud-stream-app-starters/tasklauncher-dataflow

tagv1.1.0.RELEASE

A Task Launcher implementation that invokes SCDF's REST-API to launch Tasks

created time in 6 days

push eventspring-cloud-stream-app-starters/jdbc

Soby Chacko

commit sha 885db163a7697c8f7730e23b5738bb1d77448d58

Next version - 2.1.5.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/gemfire

Soby Chacko

commit sha d14e1154f7cb5ac9922e8fd0f2c9875713e8c381

Next version - 2.1.5.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/rabbit

Soby Chacko

commit sha 7999318f6344e559b5032912191fad9a90a83a8b

Next version - 2.1.4.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/httpclient

Soby Chacko

commit sha 93648f835684d92761f57713a326408b7acfc6f1

Next version - 2.1.4.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/router

Soby Chacko

commit sha cbae324185297aead3e00d60920f3338d0ae16f5

Next version - 2.1.4.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/header-enricher

Soby Chacko

commit sha a123e517f86b27f68c8fde2d60089d3a3aa31235

Next version - 2.1.4.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/log

Soby Chacko

commit sha b804cfbb1e976eb42b276bea81a836dc4f228f6a

Next version - 2.1.4.BUILD-SNAPSHOT

view details

push time in 6 days

created tagspring-cloud-stream-app-starters/log

tagv2.1.3.RELEASE

Log application starters

created time in 6 days

push eventspring-cloud-stream-app-starters/analytics

Soby Chacko

commit sha 56fce08b5c46e2e43dd02693eb7049ecd4222b31

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/python

Soby Chacko

commit sha 126b25ddd4b313b324383890b2a2e26a3db43260

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/hdfs

Soby Chacko

commit sha 35a3337c3f70d730968a5a17ecd464d69acede37

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/mongodb

Soby Chacko

commit sha 2ca9729fcb39476113a35dc1be102fd4b01ad60f

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/tensorflow

Soby Chacko

commit sha 30ddf1d46cb8cdcc8647ea0385700d20d7e60f01

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/sftp

Soby Chacko

commit sha 97a3a18a6b3384431417a6e78c648b5a760ef5ce

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/aws-s3

Soby Chacko

commit sha a5ae0469cdfe95913a734f71a3e932fc5c52d096

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/file

Soby Chacko

commit sha 1fc34271871b9ce157ac7743907ccb2bd3d674dc

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/ftp

Soby Chacko

commit sha 2ced1dfd41b9e1fae3f777e798995e7d70d261e7

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

created tagspring-cloud-stream-app-starters/ftp

tagv2.1.2.RELEASE

created time in 6 days

push eventspring-cloud-stream-app-starters/scriptable-transform

Soby Chacko

commit sha 82dafa931d9573b96327e781b7c6f1919a95c848

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/splitter

Soby Chacko

commit sha 31c3b2cbf7015570f1dfec17fd88a9be2eec2344

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/aggregator

Soby Chacko

commit sha 664949b19aad6b46dc8a7c50a8f160e6207cfc1a

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

created tagspring-cloud-stream-app-starters/aggregator

tagv2.1.2.RELEASE

The Spring Cloud Stream Aggregator Application Starter

created time in 6 days

push eventspring-cloud-stream-app-starters/mqtt

Soby Chacko

commit sha 2bef970516c5139e4887908cc76563b1aab110f2

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/twitter

Soby Chacko

commit sha 5c9636d3cc4f368624f87c9c51ce7f5a91279791

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/cassandra

Soby Chacko

commit sha 67efac7f97dc774e6ff008f397d360d41e577430

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

push eventspring-cloud-stream-app-starters/tcp

Soby Chacko

commit sha ac10642790331f82df383f8af992981746a12602

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

created tagspring-cloud-stream-app-starters/tcp

tagv2.1.2.RELEASE

created time in 6 days

push eventspring-cloud-stream-app-starters/redis-pubsub

Soby Chacko

commit sha 42385d1c22f096d92554cf2f44a1c811a89e0971

Next version - 2.1.3.BUILD-SNAPSHOT

view details

push time in 6 days

more