Re: [ANNOUNCE] New Apache Apex PMC Member: Siyuan Hua

Congrats Siyuan :) -Priyanka On Thu, Jun 16, 2016 at 10:19 AM, Pradeep Kumbhar wrote: > Congratulations Siyuan!! > > On Thu, Jun 16, 2016 at 10:17 AM, Teddy Rusli > wrote: > > > Congrats Siyuan! > > > > On Wed, Jun 15, 2016 at 9:28 PM, Ashwin

Re: Bleeding edge branch ?

+1 for creating such branch. One of us will have to rebase it with master branch at intervals. I don't think everyone will cherry-pick their commits here. We can make it once in a month activity. Are we considering updating all dependency library version as well? -Priyanka On Tue, Jul 12, 2016

Re: Using DSL api to construct sql queries

> timothytiborfar...@gmail.com> wrote: > > > I see, cool :) > > > > On Thu, Jul 21, 2016 at 9:21 AM, Priyanka Gugale <pri...@apache.org> > > wrote: > > > > > Hi Tim, > > > > > > We are not creating our own DSL, the jooq is just anoth

Need suggestion on jooq ASL License

Hi, I have used jooq library (ASL licensed) in new updates to JDBC input operator. Here is the licensing information of library: http://www.jooq .org/legal/licensing License says it *depends but doesn't bundle* those non ASL license dependencies. As per my understanding those will be included

Re: Using DSL api to construct sql queries

> > On Thu, Jul 21, 2016 at 11:13 PM, Chinmay Kolhatkar < > chin...@datatorrent.com > > wrote: > > > Yes there is no clash with calcite integration. Calcite is a query > planner > > converts SQL to a relational algebra... This is different. > > &

Re: Need suggestion on jooq ASL License

> > Can you list all added dependencies (transitively) that are added to the > pom by your change? > > On Mon, Aug 1, 2016 at 8:04 AM, Priyanka Gugale <pri...@apache.org> wrote: > > > Hi, > > > > I have used jooq library (ASL licensed) in new update

Re: [ANNOUNCE] New Apache Apex Committer: Devendra Tagare

Congrats Dev!! -Priyanka On Thu, Aug 11, 2016 at 11:45 AM, Yogi Devendra < devendra.vyavah...@gmail.com> wrote: > Congratulations Dev !!! > > ~ Yogi > > On 11 August 2016 at 11:37, Chinmay Kolhatkar > wrote: > > > Congrats Dev!! > > > > On Thu, Aug 11, 2016 at 10:50

Re: Using DSL api to construct sql queries

ences > > for SQL. > > > > However, the licensing does not seem to be straightforward. Please check: > > http://www.jooq.org/legal/licensing. Can this be used as a dependency in > > Apex? > > > > ~ Bhupesh > > > > On Wed, Jul 20, 2016 at 3:06 AM, Priyanka Gugale <

Re: Using DSL api to construct sql queries

rty and then allow standard sql to be specified. There are already > mature Apache License SQL parsers which support many different SQL > implementations. > > https://github.com/JSQLParser/JSqlParser > > Thanks, > Tim > > On Thu, Jul 21, 2016 at 2:19 AM, Priyanka Gugale <p

Re: Solving JIRA ISUUE : APEXMALHAR-2016.

Hi Harsh, This seems to be a backward incompatible change, so I would suggest let's wait to fix it till next major release when we can change the api. One option could be, deprecate current function and add new function with same name which accepts Set as parameter. But I am not sure how

Re: Running application built against custom Malhar version

As per maven documentation, the "system" scope is similar to "provided" scope. That means jre or platform is suppose to provide the jar at runtime. Normally, Malhar library jar is included in uber jar and is not at provided scope when we build an apa. That's why your application can't locate the

Re: Malhar 3.5.0 release

APEXMALHAR-2171 PR is open: https://github.com/apache/apex-malhar/pull/358 -Priyanka On Fri, Aug 5, 2016 at 12:32 PM, Yogi Devendra wrote: > Fix for APEXMALHAR-2176 > PR open: https://github.com/apache/apex-malhar/pull/361 > > ~ Yogi > > On 1 August 2016 at

Update to AbstractJDBCPollInputOperator

Hi, The poll operator in repository has n-1 non-polling partition to read DB in parallel fashion whereas the last partition keeps polling DB to fetch newly added records. *For non-polling Partition,* To assign range of rows to read to a partition we first fire a offset, limit query to fetch key

Re: JDBC Poller implementation

le concrete implementations > just because we want the same data in different formats. Ports should serve > the purpose. > > ~ Bhupesh > > > On Mon, Aug 8, 2016 at 4:46 PM, Priyanka Gugale <priya...@datatorrent.com> > wrote: > > > Hi, > > > > JD

StrAM event grouping

Hi, StrAM raises events whenever Operator or Container restarts. In Apex Dag whenever a container/operator, say operator "X", is killed/terminated all downstream operators are redeployed. And during redeploy process they raise stop/start events. These events are triggered by redeployment of

Re: Schema Discovery Support in Apex Applications

+1 to have this feature. -Priyanka On Tue, Jan 17, 2017 at 9:18 PM, Pramod Immaneni wrote: > +1 > > On Mon, Jan 16, 2017 at 1:23 AM, Chinmay Kolhatkar > wrote: > > > Hi All, > > > > Currently a DAG that is generated by user, if contains any POJOfied

Re: [DISCUSS] Proposal for adapting Malhar operators for batch use cases

Will it make an impression on user that, if he has a batch usecase he has to use batch aware operators only? If so, is that what we expect? I am not aware of how do we implement batch scenario so this might be a basic question. -Priyanka On Mon, Jan 16, 2017 at 12:02 PM, Bhupesh Chawda

Re: Upgrade Apache Bigtop to Apex Core 3.5.0

+1 On Fri, Jan 20, 2017 at 9:25 AM, Chinmay Kolhatkar wrote: > Sanjay, > Its not a lot of work. Just a version change, but primarily follwing apache > process for bigtop. > Powered by Page of bigtop is here: >

Re: GenericFileOutputOpeator doesn't work for all hadoop file systems

I would suggest, we override "openStream" in GenericFileOutputOpeator, as suggested in option 2 and then handle "append" in different way for FS which doesn't support append. Or else create concrete classes for all file systems which don't support append and override the required functions. -1

Re: Testing operators / CI

As I have seen so far, most of the data store systems have mock or embedded servers mainly used for testing. We should try to use them as much as possible. For data systems which don't have embedded/mock server for those I/O operators only will need to follow some different strategy for coverage.

Re: [ANNOUNCE] New Apache Apex PMC Member: Chandni Singh

Congrats Chandni. -Priyanka On Tue, Sep 13, 2016 at 10:39 AM, Yogi Devendra < devendra.vyavah...@gmail.com> wrote: > Congratulations !!! > > ~ Yogi > > On 13 September 2016 at 10:30, Tushar Gosavi > wrote: > > > Congratulations Chandni > > > > - Tushar. > > > > > > On

Re: Trying to acces live data

Hi Hitesh, Can you collect all logs including app master logs and send it? Run command "yarn logs -applicationId " on cluster to get logs for an application. Also please collect stderr output logs of appMaster. You can find them under "/logs/userlogs///" -Priyanka On Fri, Sep 23, 2016 at 10:55

Writing to external systems in reconciled fashion

Dear community, We had a discussion before about having reconciler for writing to JDBC output operator. I am proposing to write a reconciler plugin which should be generic

Re: Writing to external systems in reconciled fashion

Hi, Please refer to this link for earlier discussion reference: https://lists.apache.org/list.html?dev@apex.apache.org -Priyanka On Thu, Sep 29, 2016 at 5:46 PM, Priyanka Gugale <priya...@datatorrent.com> wrote: > Dear community, > > We had a discussion > <https://mai

Re: data pull from JDBC

Hi Vinod, For Pojo, you need to define a class having all of your fields (which will be populated by data retrieved from jdbc table). In this class you also need to define getter/setter for each field. When you use JdbcPOJOInputOperator, provide the fully classified class name as input to this

Re: Need help to initialize a list from properties.xml

+1 for having different name of setter. Having overloaded setter could cause confusion to BeanUtils. I would suggest two options: 1. Accept a json of column to POJO mappings 2. Explore bean utils to set list of objects from properties file. This is little tricky, you might have to write your own

Re: (APEXMALHAR-2340) Initialize the list of JdbcFieldInfo in JdbcPOJOInsertOutput operator from properties.xml

+1 for having json based input for mappings. -Priyanka On Mon, Nov 14, 2016 at 11:21 PM, Devendra Tagare wrote: > Hi, > > CSV schemas formats are based on delimited schemas which are meant to be > sequence sensitive ref : DelimitedSchema >

Re: Adding new log4j appender to Apex core

ation is ultimately owned by the user, so how do you > want > to enforce a custom appender? > > I don't think that this should rely on anything in ~/.dt either > > Thomas > > On Tue, Nov 22, 2016 at 10:00 AM, Priyanka Gugale < > priya...@datatorrent.com> &

Re: Apex internal documentation.

+1 for documenting this. I had covered the basic cycle of launch in couple of meetups but there is no documentation. Also many things like bufferserver management, heartbeat mechanism, command execution, stats etc are not documented. -Priyanka On Tue, Nov 29, 2016 at 11:23 AM, Tushar Gosavi

Adding new log4j appender to Apex core

Hi, I am working on APEXCORE-563 As per this Jira we should put log file name in container/operator events. The problem is current RollingFileAppender keeps renaming files from 1 to 2 to ... n as files reach maximum allowed file size. Because

Re: APEXMALHAR-2382 User needs to create dt_meta table while using JdbcPOJOInsertOutputOperator

IMO it's okay to create table in java code. We should document it in operator guide as well as put a log message when we create table. And in case you don't have privileges, the operator should throw meaningful message. -Priyanka On Fri, Jan 13, 2017 at 4:07 PM, Yogi Devendra

Re: Changes for calling committed on operators when stream locality is THREAD_LOCAL

CheckpointNotificationListener extends CheckpointListener and hence "committed" method is going to be there. So I think other operator who tires to use "committed" with THREAD_LOCAL combination in future will also suffer this behavior. I would suggest we should fix it in platform. We should think

Re: Programmatic log4j appender in Apex

We can always write a custom appender and add it by changing root appender in log4j config file. Can you explain how adding appender grammatically would help? -Priyanka On Sun, Apr 9, 2017 at 11:50 AM, Sanjay Pujare wrote: > Please give some examples and/or use cases of

Re: Enhancement to support custom SSL configuration

+1 for this support, it's important to let users use their own own keystore files. Is it okay to distribute files inside our package along with jar/resources, are there any security restrictions? Or we should use other medium like HDFS or other shared file system to host these key files?

Re: Package tarball as deliverable of apex-core

Hi Chinmay, How about using linux distributions like deb/rpm, why create one more way of distribution? -Priyanka On Tue, Aug 8, 2017 at 8:34 AM, Chinmay Kolhatkar wrote: > Dear Community, > > Currently Apache Apex does not have a deliverable tarball which bundles the

Re: Proposal to upgrade Apex Core dependency in Malhar to 3.6

+1 to upgrade dependency version. -Priyanka On Thu, May 11, 2017 at 7:22 PM, Thomas Weise wrote: > +1 for upgrade to 3.6 > > https://issues.apache.org/jira/browse/APEXMALHAR-2471 > > > On Thu, May 11, 2017 at 5:51 AM, AJAY GUPTA wrote: > > > Hi all, > >

Re: impersonation and application path

+1 for proposal. Can we make new behaviour of writing to users own directory as default? Most probably users will upgrade gateway with apex-core. If not, they always have option to set the flag and fall back to legacy behaviour. -Priyanka On Fri, May 19, 2017 at 7:52 AM, Chinmay Kolhatkar

Re: checking dependencies for known vulnerabilities

I had one more point to add. During adding such checks we should think of all types of contributors. We don't want to make it very difficult to people to get in their PR, it will discourage people from putting any code changes. Ultimately we want to grow as a community where we would like people

Re: checking dependencies for known vulnerabilities

It's good idea to check for vulnerabilities, but as Pramod said all softwares / libraries are going to have some or other vulnerability at any time. I will go with approach of "let's discuss this addition" and we should not affect PRs which are not adding any new dependencies (due to old

Re: [DISCUSS] inactive PR

Hi, I am okay with closing inactive PR but timeline should be more than a month. I have been in situations where for some reason or other the PR was pending for 2-3 months, sometimes reason was simple as relevant committer didn't have time to review that time. I will vote for 3 months. -Priyanka

Re: [VOTE] Major version change for Apex Library (Malhar)

Apologies for being late in discussions. I wanted to understand one thing. As Thomas mentioned some of our operators are not matured enought or lacks operability. Do we know if such operators need any backword incompatible changes? e.g. modification to api etc? Do we have plan to promote operators

Re: [Proposal] Simulate setting for application launch

+1 Sometimes this context is required. We shouldn't change any default behaviour other than making this config available. -Priyanka On Wed, Dec 20, 2017 at 5:32 AM, Pramod Immaneni wrote: > The external system recording was just an example, not a specific use case. >

Re: [ANNOUNCE] New Apache Apex Committer: Ananth Gundabattula

Congrats Ananth!! -Priyanka On Fri, Nov 3, 2017 at 2:20 PM, Thomas Weise wrote: > The Project Management Committee (PMC) for Apache Apex is pleased to > announce Ananth Gundabattula as new committer. > > Ananth has been contributing to the project for about a year. Highlights:

Re: [ANNOUNCE] New Apache Apex PMC: Tushar Gosavi

;3. http://www.apexbigdata.com/pune-integration-talk-4.html > >4. Webinar on Smart Partitioning with Apex. ( > >https://www.youtube.com/watch?v=HCATB1zlLE4 > ><https://www.youtube.com/watch?v=HCATB1zlLE4>) > >5. Presented about customer use case at Pune Meetup in 2016 > > > > Pramod for the Apache Apex PMC. > > > -- ___ *Priyanka Gugale* Software Engineer E: priya...@datatorrent.com | M: +91 9923316831 | Twitter: @ggl_priyanka www.datatorrent.com | apex.apache.org

Re: [ANNOUNCE] New Apache Apex PMC Member: Chinmay Kolhatkar

Congrats Chinmay!! -Priyanka On Fri, May 25, 2018, 11:15 AM vikram patil wrote: > Congratulations Chinmay !!! > > On Fri, May 25, 2018 at 11:00 AM, Ashwin Chandra Putta > wrote: > > Congrats Chinmay. Well deserved. > > > > On Thu, May 24, 2018

Re: [DISCUSS] Time for attic?

I do believe and know of some work done in private forks by people. There could be couple of reasons why it didn't go public. One could be high bar for code submission (I don't have references at hand but that's general feeling amongst committers) and other could be lack of motivation. Let's try

Re: Contribution and committer guidelines

Hi, IMO let's not spend lot of time in digging up past just to check proofs for people's opinion like hight bar for code submission or long pending reviews. If it's a common feeling amongst most of committers and they are saying it, we should find some way to work our way to improve things. May

[jira] [Commented] (APEXMALHAR-2103) scanner issues in FileSplitterInput class

[ https://issues.apache.org/jira/browse/APEXMALHAR-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308863#comment-15308863 ] Priyanka Gugale commented on APEXMALHAR-2103: - Hi, I think the problem is not with wrong

[jira] [Assigned] (APEXMALHAR-2041) Write Cassandra application tests using embedded server

[ https://issues.apache.org/jira/browse/APEXMALHAR-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale reassigned APEXMALHAR-2041: --- Assignee: Priyanka Gugale > Write Cassandra application tests us

[jira] [Created] (APEXMALHAR-2121) KafkaInputOperator emitTuple method should be able to emit more than just message

Priyanka Gugale created APEXMALHAR-2121: --- Summary: KafkaInputOperator emitTuple method should be able to emit more than just message Key: APEXMALHAR-2121 URL: https://issues.apache.org/jira/browse

[jira] [Created] (APEXMALHAR-2172) Update JDBC poll input operator to fix issues

Priyanka Gugale created APEXMALHAR-2172: --- Summary: Update JDBC poll input operator to fix issues Key: APEXMALHAR-2172 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2172 Project: Apache

[jira] [Created] (APEXMALHAR-2184) Add documentation for FileSystem Input Operator

Priyanka Gugale created APEXMALHAR-2184: --- Summary: Add documentation for FileSystem Input Operator Key: APEXMALHAR-2184 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2184 Project: Apache

[jira] [Created] (APEXMALHAR-2161) Add tests fir AbstractThroughputFileInputOperator

Priyanka Gugale created APEXMALHAR-2161: --- Summary: Add tests fir AbstractThroughputFileInputOperator Key: APEXMALHAR-2161 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2161 Project

[jira] [Updated] (APEXMALHAR-2161) Add tests for AbstractThroughputFileInputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXMALHAR-2161: Summary: Add tests for AbstractThroughputFileInputOperator (was: Add tests

[jira] [Created] (APEXMALHAR-2163) User query dsl api to construct SQL query

Priyanka Gugale created APEXMALHAR-2163: --- Summary: User query dsl api to construct SQL query Key: APEXMALHAR-2163 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2163 Project: Apache Apex

[jira] [Created] (APEXMALHAR-2179) Add documentation for JDBCPollInputOperator

Priyanka Gugale created APEXMALHAR-2179: --- Summary: Add documentation for JDBCPollInputOperator Key: APEXMALHAR-2179 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2179 Project: Apache

[jira] [Assigned] (APEXCORE-602) Provide a "group-id" in the event object so that events are grouped together by a "root cause".

[ https://issues.apache.org/jira/browse/APEXCORE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale reassigned APEXCORE-602: Assignee: Priyanka Gugale > Provide a "group-id" in the ev

[jira] [Resolved] (APEXMALHAR-2418) Update the twitter library to 4.0.6

[ https://issues.apache.org/jira/browse/APEXMALHAR-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXMALHAR-2418. - Resolution: Fixed Assignee: (was: Priyanka Gugale) Fix

[jira] [Assigned] (APEXMALHAR-2418) Update the twitter library to 4.0.6

[ https://issues.apache.org/jira/browse/APEXMALHAR-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale reassigned APEXMALHAR-2418: --- Assignee: Priyanka Gugale > Update the twitter library to 4.

[jira] [Created] (APEXMALHAR-2232) Add documentation for csv parser

Priyanka Gugale created APEXMALHAR-2232: --- Summary: Add documentation for csv parser Key: APEXMALHAR-2232 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2232 Project: Apache Apex Malhar

[jira] [Updated] (APEXMALHAR-2232) Add documentation for csv parser

[ https://issues.apache.org/jira/browse/APEXMALHAR-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXMALHAR-2232: Priority: Minor (was: Major) > Add documentation for csv par

[jira] [Updated] (APEXMALHAR-2255) Use latest couchbase client library

[ https://issues.apache.org/jira/browse/APEXMALHAR-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXMALHAR-2255: Summary: Use latest couchbase client library (was: Use latest java sdk

[jira] [Commented] (APEXMALHAR-2255) Use latest java sdk for couchbase

[ https://issues.apache.org/jira/browse/APEXMALHAR-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512385#comment-15512385 ] Priyanka Gugale commented on APEXMALHAR-2255: - The request is to upgrade *couchbase java

[jira] [Created] (APEXMALHAR-2255) Use latest java sdk for couchbase

Priyanka Gugale created APEXMALHAR-2255: --- Summary: Use latest java sdk for couchbase Key: APEXMALHAR-2255 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2255 Project: Apache Apex Malhar

[jira] [Assigned] (APEXCORE-561) Container info needs to be persisted even after application has been killed

[ https://issues.apache.org/jira/browse/APEXCORE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale reassigned APEXCORE-561: Assignee: Priyanka Gugale > Container info needs to be persisted even af

[jira] [Commented] (APEXCORE-562) RecordingsAgent: returns records for offset beyond number of tuples

[ https://issues.apache.org/jira/browse/APEXCORE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588531#comment-15588531 ] Priyanka Gugale commented on APEXCORE-562: -- getTuplesInfo function incorrectly updates current

[jira] [Updated] (APEXCORE-562) RecordingsAgent: returns records for offset beyond number of tuples

[ https://issues.apache.org/jira/browse/APEXCORE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXCORE-562: - Affects Version/s: 3.4.0 > RecordingsAgent: returns records for offset beyond num

[jira] [Commented] (APEXCORE-562) RecordingsAgent: returns records for offset beyond number of tuples

[ https://issues.apache.org/jira/browse/APEXCORE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588709#comment-15588709 ] Priyanka Gugale commented on APEXCORE-562: -- [~thw] please add me as contributor in the JIRA

[jira] [Commented] (APEXCORE-564) We should be able to remove loggers level settings

[ https://issues.apache.org/jira/browse/APEXCORE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15601132#comment-15601132 ] Priyanka Gugale commented on APEXCORE-564: -- Our initial though was, we will set it to NULL so

[jira] [Commented] (APEXMALHAR-2272) sequentialFileRead property on FSInputModule not functioning as expected

[ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15584507#comment-15584507 ] Priyanka Gugale commented on APEXMALHAR-2272: - done. > sequentialFileRead prope

[jira] [Commented] (APEXCORE-564) We should be able to remove loggers level settings

[ https://issues.apache.org/jira/browse/APEXCORE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605201#comment-15605201 ] Priyanka Gugale commented on APEXCORE-564: -- okay closing the issue in that case. > We sho

[jira] [Closed] (APEXCORE-564) We should be able to remove loggers level settings

[ https://issues.apache.org/jira/browse/APEXCORE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale closed APEXCORE-564. Resolution: Won't Fix > We should be able to remove loggers level setti

[jira] [Closed] (APEXCORE-578) Amend javadoc syntax in AbstractUpsertOutputOperator

[ https://issues.apache.org/jira/browse/APEXCORE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale closed APEXCORE-578. Resolution: Invalid Opened in error. > Amend javadoc syn

[jira] [Created] (APEXMALHAR-2356) Amend javadoc syntax in cassandra upsert operators

Priyanka Gugale created APEXMALHAR-2356: --- Summary: Amend javadoc syntax in cassandra upsert operators Key: APEXMALHAR-2356 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2356 Project

[jira] [Resolved] (APEXMALHAR-2325) Same block id is emitting from FSInputModule

[ https://issues.apache.org/jira/browse/APEXMALHAR-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXMALHAR-2325. - Resolution: Fixed Fix Version/s: 3.6.0 > Same block id is emitt

[jira] [Created] (APEXCORE-564) We should be able to remove loggers level settings

Priyanka Gugale created APEXCORE-564: Summary: We should be able to remove loggers level settings Key: APEXCORE-564 URL: https://issues.apache.org/jira/browse/APEXCORE-564 Project: Apache Apex

[jira] [Resolved] (APEXMALHAR-2330) JdbcPOJOPollInputOperator fails with NullPointerException when PostgreSQL driver

[ https://issues.apache.org/jira/browse/APEXMALHAR-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXMALHAR-2330. - Resolution: Fixed Fix Version/s: 3.7.0 > JdbcPOJOPollInputOpera

[jira] [Created] (APEXMALHAR-2367) CassandraTransactionalStore should handle erroneous records

Priyanka Gugale created APEXMALHAR-2367: --- Summary: CassandraTransactionalStore should handle erroneous records Key: APEXMALHAR-2367 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2367

[jira] [Commented] (APEXCORE-602) Provide a "group-id" in the event object so that events are grouped together by a "root cause".

[ https://issues.apache.org/jira/browse/APEXCORE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085875#comment-16085875 ] Priyanka Gugale commented on APEXCORE-602: -- Testing covered: 1. Wrote unit tests 2. Simulated

[jira] [Updated] (APEXCORE-756) Fix test failure in GroupingManager

[ https://issues.apache.org/jira/browse/APEXCORE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXCORE-756: - Summary: Fix test failure in GroupingManager (was: Fix test failure in GropingManager

[jira] [Created] (APEXCORE-756) Fix test failure in GropingManager

Priyanka Gugale created APEXCORE-756: Summary: Fix test failure in GropingManager Key: APEXCORE-756 URL: https://issues.apache.org/jira/browse/APEXCORE-756 Project: Apache Apex Core

[jira] [Updated] (APEXCORE-756) Fix ConcurrentModificationException in GroupingManager

[ https://issues.apache.org/jira/browse/APEXCORE-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXCORE-756: - Summary: Fix ConcurrentModificationException in GroupingManager (was: Fix test failure

[jira] [Updated] (APEXMALHAR-2487) Malhar should support outputting data in Snappy compression

[ https://issues.apache.org/jira/browse/APEXMALHAR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale updated APEXMALHAR-2487: Fix Version/s: 3.8.0 > Malhar should support outputting data in Sna

[jira] [Resolved] (APEXMALHAR-2487) Malhar should support outputting data in Snappy compression

[ https://issues.apache.org/jira/browse/APEXMALHAR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXMALHAR-2487. - Resolution: Fixed > Malhar should support outputting data in Sna

[jira] [Resolved] (APEXMALHAR-2447) No indication from AbstractFileInputOperator when directory is empty

[ https://issues.apache.org/jira/browse/APEXMALHAR-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXMALHAR-2447. - Resolution: Fixed Fix Version/s: 3.8.0 > No indication f

[jira] [Resolved] (APEXMALHAR-2535) Timeouts in AbstractEnricher specified as int which limits duration of time which could be specified.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXMALHAR-2535. - Resolution: Fixed Fix Version/s: 3.8.0 > Timeouts in AbstractEnric

[jira] [Assigned] (APEXMALHAR-2535) Timeouts in AbstractEnricher specified as int which limits duration of time which could be specified.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale reassigned APEXMALHAR-2535: --- Assignee: Tushar Gosavi > Timeouts in AbstractEnricher specified as

[jira] [Resolved] (APEXCORE-792) LoggerUtil should allow to get LogFileInformation for a specified logger

[ https://issues.apache.org/jira/browse/APEXCORE-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyanka Gugale resolved APEXCORE-792. -- Resolution: Fixed Fix Version/s: 3.7.0 > LoggerUtil should allow to

[jira] [Commented] (APEXCORE-792) LoggerUtil should allow to get LogFileInformation for a specified logger

[ https://issues.apache.org/jira/browse/APEXCORE-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16233667#comment-16233667 ] Priyanka Gugale commented on APEXCORE-792: -- Can you please specify use case for this change