GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/31
added new config for job.changelog.system
SAMZA-1060.
Allow to specify a changelog system separately, so user can only specify
stream name for each store.
If user specifies both (system and
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/32
add docs for the new job.changelog.system config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza master
Alternatively you can review
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/36
JavaStorageConfig handling job.changelog.system
SAMZA-1066
Same as change for StorageConfig.java
Allows user to set changelog system in job.changelog.system and specify
stream only in
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/39
SAMZA-1076: getKafkaChangelogEnabledStores() should use
StorageConfig.getChangeloâ¦
getKafkaChangelogEnabledStores() should use
StorageConfig.getChangelogStream to get changelog system.stream
You
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/49
Schedule after debounce time
Allows scheduling an action (a Runnable) after some de-bounce delay.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/50
Zk controller
Added ZKController and ZkControllerImpl
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza ZkController
Alternatively you
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/52
SAMZA-1086. New Grouper for ZK based standalone.
SAMZA-1086.
Create new grouper with support for arbitrary container ids.
You can merge this pull request into a Git repository by running
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/61
SAMZA-1103: ZkBarrier
SAMZA-1103: Barrier for JobModel upgrades. When all the processors got
notification about the new JobModel, only after that they can start using the
new model.
You can merge
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/64
SAMZA-1064:Zk test utils
Some test utils needed for StandAlone zk based testing.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/67
SAMZA-1107:Job model publish
add utils for publishing job model and job model version to ZK.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/64
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/70
SAMZA-1115:Job coordinator
Job coordinator to work with the ZooKeeper.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza JobCoordinator
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/77
SAMZA-1124:Job coordinator with time out
If a processor doesn't join the barrier for the TimeOut time - the barrier
is cancelled. All the processor should unsubscribe from it.
You can merge this
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/81
SAMZA-1134:Simplify barrier for zk version upgrade.
see SAMZA-1134 for details.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/91
SAMZA-1151. Coordination service.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza CoordinationService
Alternatively you can review
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/70
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/122
SAMZA-1210: Fixing merge issue and container id generations.
This PR is just for fixing issues introduced by a merge and changing
container id generation.
You can merge this pull request into a Git
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/156
SAMZA-1257: make sure a dataChange listener in LeaderElection is always
initialized.
@xinyuiscool, @navina please review.
You can merge this pull request into a Git repository by running:
$ git
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/157
SAMZA-1258. Integration tests. Happy Path.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza unitTestHappyPath3
Alternatively you can
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/178
SAMZA-1258. Integration tests. Happy Path.
This is reincarnation of PR #157
It was not possible to merge/rebase that branch, so I had to create another
one and reapply the changes.
You can
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/180
SAMZA-1064: Do not process onProcessorChange if list of children is null.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/181
SAMZA-1193. re-enable the test
TestZkBarrierForVersionUpgrade.testZkBarrierForVersionUpgrade
The code changed significantly. I've rerun the test multiple times both
with gradle and inteli
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/185
SAMZA-1286: Close zk connection in ZkController.stop()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza ZkControllerClose
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/157
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/192
SAMZA-1291: Stand alone config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza StandAloneConfig
Alternatively you can review and
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/197
SAMZA-1298: Create zk path.
if ZK path contains extra path at the end, it needs to be created in ZK at
first connect.
You can merge this pull request into a Git repository by running:
$ git
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/198
SAMZA-1305. SAMZA-1306. Unit test - zk unavailable.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza unitTestZkUnavailable2
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/200
DO NOT REVIEW YET. changed processor ids for different partiicipants
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/203
SAMZA-1309. Debounce time config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza DebounceConfig
Alternatively you can review and
GitHub user sborya reopened a pull request:
https://github.com/apache/samza/pull/203
SAMZA-1309. Debounce time config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza DebounceConfig
Alternatively you can review and
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/203
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/206
SAMZA-1313. Rename StandaloneJobCoordinator to PassthroughJobCoordinator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/200
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/216
SAMZA-1326: Revert to use getGlobalAppId for zk path
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza getGlobalId
Alternatively you
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/217
SAMZA-1327: create zk namespace if does not exist
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza zkNamespaceCreate
Alternatively
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/218
SAMZA-1327: fail if namespace specified in the connection string does not
exist
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/220
SAMZA-1330: Stand alone feature preview, known limitation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza StandAloneFeaturePreview
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/217
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/229
Session fail reregister
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza SessionFailReregister
Alternatively you can review and
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/231
SAMZA-1337: Use StreamTask with the LocalApplicationRunner
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/238
SAMZA-1165. Zk clean up old versions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza zkCleanUpBarrier
Alternatively you can review
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/238
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/239
SAMZA-1165. cleanup old zk versions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza zkCleanUpBarrier1
Alternatively you can review
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/247
SAMZA-1368: make sure new job model will be generated in case of barrier
timeout.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/255
SAMZA-1382: added Zk communication protocol version verification
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/262
SAMZA-1173: Refactor zk coordination utils
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza RemoveZkCoordinationUtils1
Alternatively
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/267
Zk lock example
This is a suggestion on ZkLock implementation. PR is not ready for final
review.
@navina
@PawasChhokra
You can merge this pull request into a Git repository by running
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/271
Refactor coordination utils (with the ZkLock)
please ignore these changes (they come form Pawas' pr #264 ):
TestStatefulTask.scala
TestKafkaSystemAdminJava.java
KafkaSystemAdmin.
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/275
SAMZA-1397: log.debug loop to run only if debug is enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza LocalityLogDebug
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/282
Coordination utils factory
Some refactoring and cleanup.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza CoordinationUtilsFactory
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/284
SAMZA-1385: Coordination utils factory with distributed lock
this PR includes some changes from another PR. I will re-merge it again,
after the other PR is in.
You can merge this pull request into a
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/267
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/271
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/262
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/290
SAMZA-1413: Config for CoordinationUtilsFactory class name.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/299
SAMZA-1427: use systemFactory in checkpoint manager.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza LiKafkaClient
Alternatively
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/304
added Boris as a committer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza addCommitter
Alternatively you can review and apply
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/314
SAMZA-1442: use systemAdmin.validateStream in KafkaCheckpointManager
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/325
Change log require kafka system admin
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza ChangeLogRequireKafkaSystemAdmin
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/330
Disable info in checkpoint logging
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza disableWriteCheckpointLogging
Alternatively you
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/330
---
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/335
StreamOperatorTask does not need to be final.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza master
Alternatively you can review
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/335
---
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/336
StreamOperatorTask does not need to be final.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza UnmakeStreamOperatorTaskFinal
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/337
TestExecutionPlanner compilation error
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
TestExecutionPlannerCompilationError
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/346
Admin GetPartitionsCount should return count and not fake
SamzaPartitionsMetadata
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/346
---
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/551
Fix loadDefaults error msg.
SAMZA-1744
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza loadDefaultsErrorMsg
Alternatively you can
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/559
Added timestamp to Incoming message envelope.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza kafkaTS
Alternatively you can review
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/597
SAMZA-1769. Remote app runner status
Call for 'status' or 'kill' does not require Execution plan calculation.
You can merge this pull request into a Git repository by running:
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/613
String format params fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza StringFormatParams
Alternatively you can review and apply
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/624
New consumer for kafka system
Remove SimpleConsumer and BrokerProxy from Samza's KafkaSystemConsumer
implementation.
Instead use KafkaConsumerProxy with high-level kafka consumer.
You can
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/647
SAMZA-1868: New kafka consumer admin (using high level consumer)
Rewrite of KafkaSystemAdmin in java, using new KafkaSystemConsumer (based
on high level kafka consumer).
You can merge this pull
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/662
SAMZA-1868: Create new SamzaAmdmin for Kafka
This Request is a copy of #647(got garbled). This PR already addresses all
the comments brought up in the other request.
You can merge this pull request
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/647
---
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/705
SAMZA-1934: creating a LegacyTaskApplication fails.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza LegacyTaskApp
Alternatively you
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/738
Kafka consumer improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza KafkaConsumerImprovements
Alternatively you can review
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/740
Keep a version of deprecated KafkaSystemConsumer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza OldKafkaConsumer
Alternatively you
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/753
Use samza offset reset value in kafka consumer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza UseSamazResetInKafka
Alternatively
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/755
Old kafka consumer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza OldKafkaConsumer
Alternatively you can review and apply these
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/779
SAMZA-1899: Remove KafkaConfig.getKafkaSystemConsumer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/782
SAMZA-1943 Remove ExtendedSystemAdmin and deprecated getNewestOffsets
method.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/789
SAMZA-1921: upgrade to use the latest java AdminClient.
In this PR, I've refactored create/clear streams methods.
You can merge this pull request into a Git repository by running:
$ git
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/837
SAMZA-2019: add Is broadcast per stream config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza isBroadcast
Alternatively you can
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/846
SAMZA-2019: for 1 partition broadcast topic generate topic#0 config
+ address few review comments
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/847
SAMZA-2030: Config mock
Fix getOption of ScalaMapConfig to support mocking.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza
86 matches
Mail list logo
