Congratulations Chinmay!!
Regards,
Hitesh Kapoor
On Thu 24 May, 2018, 11:02 PM Ilya Ganelin, wrote:
> Congrats!
>
> On Thu, May 24, 2018, 10:09 AM Pramod Immaneni wrote:
>
> > Congratulations Chinmay.
> >
> > On Thu, May 24, 2018 at 9:39 AM Thomas Weise wrote:
+1.
--Hitesh
On Fri, Jan 19, 2018 at 12:28 AM, Ananth G wrote:
> Hello All,
>
> I was wondering if we can consider making java 8 as the minimum supported
> idk version going forward.
>
> Since Apex core is moving to the next release cycle, perhaps we consider
> this ? My assumption is that the
Congratulations Tushar.
Regards,
Hitesh Kapoor
On 03-Nov-2017 9:53 PM, "Ashwin Chandra Putta"
wrote:
> Congratulations Tushar!!
>
> Regards,
> Ashwin.
>
> On Fri, Nov 3, 2017 at 9:17 AM, Pramod Immaneni
> wrote:
>
> > A bit delayed but nevertheless im
Hitesh Kapoor created APEXMALHAR-2510:
-
Summary: Incorrect results for join accumulation in case of
duplicate keys
Key: APEXMALHAR-2510
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2510
[
https://issues.apache.org/jira/browse/APEXMALHAR-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052773#comment-16052773
]
Hitesh Kapoor commented on APEXMALHAR-2507:
---
Hi [~lushun...@gmail
[
https://issues.apache.org/jira/browse/APEXMALHAR-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050885#comment-16050885
]
Hitesh Kapoor commented on APEXMALHAR-2507:
---
HI [~lushun...@gmail.com
[
https://issues.apache.org/jira/browse/APEXCORE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor reassigned APEXCORE-662:
--
Assignee: Hitesh Kapoor
> Raise StramEvent for heartbeat m
Hitesh Kapoor created APEXMALHAR-2430:
-
Summary: Optimize Join accumulation by changing the data structure
in accumulation method
Key: APEXMALHAR-2430
URL: https://issues.apache.org/jira/browse/APEXMALHAR
Hitesh Kapoor created APEXMALHAR-2429:
-
Summary: Ambiguity in passing "key" parameter to Join accumulation
Key: APEXMALHAR-2429
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2429
[
https://issues.apache.org/jira/browse/APEXMALHAR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885429#comment-15885429
]
Hitesh Kapoor commented on APEXMALHAR-2414:
---
Fix for this issue has
Hitesh Kapoor created APEXMALHAR-2424:
-
Summary: Null pointer exception in JDBCPojoInputOperator is thrown
when we set columnsExpression and have additional columns in fieldInfos
Key: APEXMALHAR-2424
URL
[
https://issues.apache.org/jira/browse/APEXMALHAR-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2424:
--
Summary: Null pointer exception in JDBCPojoPollInputOperator is thrown when
we set
[
https://issues.apache.org/jira/browse/APEXMALHAR-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor reassigned APEXMALHAR-2415:
-
Assignee: Hitesh Kapoor
> Enable PojoInnerJoin accum to allow multiple k
[
https://issues.apache.org/jira/browse/APEXMALHAR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor reassigned APEXMALHAR-2414:
-
Assignee: Hitesh Kapoor
> Improve performance of PojoInnerJoin accum
[
https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1585#comment-1585
]
Hitesh Kapoor commented on APEXMALHAR-2239:
---
[~d9liang] Have you h
On o Zxdfxxffxd hu
On Feb 21, 2017 2:21 PM, "ASF GitHub Bot (JIRA)" wrote:
[ https://issues.apache.org/jira/browse/APEXMALHAR-2381?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&
focusedCommentId=15875616#comment-15875616 ]
ASF GitHub Bot commented on APEXMALHAR
Hitesh Kapoor created APEXMALHAR-2417:
-
Summary: Add PojoOuterJoin (left, right and full) accumulation
Key: APEXMALHAR-2417
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2417
Project
Hi All,
In PojoInnerJoin accumulation same field names are emitted as single field
even if we don't take a join on them. For example consider the following 2
POJO's on 2 streams
POJO1
{
id: Int
age : String
}
POJO2
{
id: Int
age : String
name : String
}
If we wish to take a join only o
Hi All,
I am proposing PojoOuterJoin accumulation.
We already have PojoInnerJoin accumulation.
As the name suggests this accumulation will be responsible to get outer
join on Pojo streams
on some input keys. The input and output streams (types) for this
accumulation will be the same
as that of P
[
https://issues.apache.org/jira/browse/APEXMALHAR-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2402:
--
Summary: PojoInnerJoin accumulation joins only on 1 field. (was:
PojoInnerJoin
[
https://issues.apache.org/jira/browse/APEXMALHAR-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2402:
--
Description: PojoInnerJoin accumulation joins only on 1 field. Ideally we
should
Hitesh Kapoor created APEXMALHAR-2402:
-
Summary: PojoInnerJoin accumulation joins only on 2 fields.
Key: APEXMALHAR-2402
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2402
Project: Apache
[
https://issues.apache.org/jira/browse/APEXMALHAR-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2400:
--
Summary: In PojoInnerJoin accumulation same field names are emitted as
single
Hitesh Kapoor created APEXMALHAR-2400:
-
Summary: In PojoInnerJoin accumulation same field names are
emitted as single field name
Key: APEXMALHAR-2400
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2400
[
https://issues.apache.org/jira/browse/APEXMALHAR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2399:
--
Description: In PojoInnerJoin accumulation default constructor is directly
Hitesh Kapoor created APEXMALHAR-2399:
-
Summary: In PojoInnerJoin accumulation default constructor is
directly throwing an exception which messes up in default serialization.
Key: APEXMALHAR-2399
URL: https
Hi Ambarish,
Yes you can plug in your own serializer. You will have to set the
"STREAM_CODEC" port attribute to achieve the same.
You can refer xmlParserApplication from examples repo (
https://github.com/DataTorrent/examples).
Regards,
Hitesh
On Mon, Feb 6, 2017 at 11:07 AM, Ambarish Pande <
a
[
https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2239:
--
Attachment: testJdbcPojoInputOperator.txt
Refer my comment of 28th Jan
> N
[
https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2239:
--
Comment: was deleted
(was: Refer my comment of 28th Jan)
> Null pointer except
[
https://issues.apache.org/jira/browse/APEXMALHAR-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843981#comment-15843981
]
Hitesh Kapoor commented on APEXMALHAR-2239:
---
[~d9liang] you are get
+1 it will enhance the user experience and the approach suggested by Ajay
doesn't seems to add significant overhead. Also I feel that in future it
can be enhanced further and UI can also filter the event logs based on
these log levels.
On Jan 19, 2017 10:57 PM, "AJAY GUPTA" wrote:
> Current even
[
https://issues.apache.org/jira/browse/APEXMALHAR-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor closed APEXMALHAR-2382.
-
Resolution: Won't Fix
As per the consensus on the dev email thread (attached to
[
https://issues.apache.org/jira/browse/APEXMALHAR-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2382:
--
Attachment: De_meta_mail_thread.pdf
Mail thread discussing if/how this Jira should
plicit ask by the end-user"
> is
> > > > > > important.
> > > > > >
> > > > > > > >
> > > > > >
> > > > > > > > ~ Yogi
> > > > > >
> > > > > > >
Hi All,
Currently to use JdbcPOJOInsertOutputOperator, user needs to create
"dt_meta" table to enforce
exactly-once processing semantic. If the user fails to create this table
before launching the application an exception is thrown.
To handle this scenario we can automate the process of creating t
Hitesh Kapoor created APEXMALHAR-2384:
-
Summary: Add documentation for FixedWIdthParser
Key: APEXMALHAR-2384
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2384
Project: Apache Apex Malhar
Hitesh Kapoor created APEXMALHAR-2383:
-
Summary: Add documentation for JdbcPOJOInsertOutputOperator
Key: APEXMALHAR-2383
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2383
Project: Apache
Hitesh Kapoor created APEXMALHAR-2382:
-
Summary: User should not be required to create "dt_meta" table
while using JdbcPOJOInsertOutputOperator
Key: APEXMALHAR-2382
URL: https://issues.apache.org/j
[
https://issues.apache.org/jira/browse/APEXMALHAR-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15777865#comment-15777865
]
Hitesh Kapoor commented on APEXMALHAR-2368:
---
The root cause of this i
Hitesh Kapoor created APEXMALHAR-2372:
-
Summary: Change the order of checks of table name in
populateColumnDataTypes
Key: APEXMALHAR-2372
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2372
Hitesh Kapoor created APEXMALHAR-2370:
-
Summary: Add user documenation for Xml Parser
Key: APEXMALHAR-2370
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2370
Project: Apache Apex Malhar
[
https://issues.apache.org/jira/browse/APEXMALHAR-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor reassigned APEXMALHAR-2368:
-
Assignee: Hitesh Kapoor
> JDBCPollInput operator reads extra records w
[
https://issues.apache.org/jira/browse/APEXMALHAR-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747696#comment-15747696
]
Hitesh Kapoor commented on APEXMALHAR-2368:
---
In my test scenario
8 col
Hitesh Kapoor created APEXMALHAR-2368:
-
Summary: JDBCPollInput operator reads extra records when 1.5M
records are added to a blank input table
Key: APEXMALHAR-2368
URL: https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/APEXMALHAR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2346:
--
Description: The argument to DocumentBuilder.parse() needs to be fixed as
that
[
https://issues.apache.org/jira/browse/APEXMALHAR-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2316:
--
Description:
Unable to set the tuple class attribute, getting the following stack
[
https://issues.apache.org/jira/browse/APEXMALHAR-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2357:
--
Description:
JdbcPojoOperatorApplicationTest was added as a part of APEXMALHAR
Hi All,
There seems to be an issue with Jenkins build which runs on creating a pull
request.
It is failing with "hudson.plugins.git.GitException: Could not checkout
master with start point origin/master" , refer
https://builds.apache.org/job/Apex_Malhar_PR/469/console.
Could someone suggest a corr
Hitesh Kapoor created APEXMALHAR-2357:
-
Summary: JdbcPojoOperatorApplicationTest failing intermittently
Key: APEXMALHAR-2357
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2357
Project
[
https://issues.apache.org/jira/browse/APEXMALHAR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2022:
--
Assignee: Chaitanya (was: Hitesh Kapoor)
> S3 Output Module for file c
Hitesh Kapoor created APEXMALHAR-2351:
-
Summary: Exception while fetching properties for Operators using
JdbcStore
Key: APEXMALHAR-2351
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2351
Hitesh Kapoor created APEXMALHAR-2346:
-
Summary: DocumentBuilder.parse() should take InputSource as an
argument instead of String
Key: APEXMALHAR-2346
URL: https://issues.apache.org/jira/browse/APEXMALHAR
Hitesh Kapoor created APEXMALHAR-2344:
-
Summary: Initialize the list of FieldInfo in JDBCPollInput
operator from properties.xml
Key: APEXMALHAR-2344
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2344
t;,
"pojoFieldExpression": "customerPhone",
"type":"STRING"
}
Regards,
Hitesh Kapoor
On Tue, Nov 15, 2016 at 11:41 PM, Sanjay Pujare
wrote:
> +1 for standardized JSON based mapping/schema definitions
>
> On Mon, Nov 14, 2
Hi All,
Currently in JdbcPOJOInsertOuput operator we cannot configure JdbcFieldInfo
via properties.xml and the user has to do the necessary coding in his
application.
To implement this improvement, the approach mentioned in
http://docs.datatorrent.com/application_packages/#operator-properties cou
Hitesh Kapoor created APEXMALHAR-2340:
-
Summary: Initialize the list of JdbcFieldInfo in
JdbcPOJOInsertOutput from properties.xml
Key: APEXMALHAR-2340
URL: https://issues.apache.org/jira/browse/APEXMALHAR
h
> wrote:
>
> > Try changing *setFieldInfo* to* setFieldInfoItem*
> >
> > Ram
> >
> > On Mon, Nov 7, 2016 at 4:23 AM, Hitesh Kapoor
> > wrote:
> >
> > > Hi All,
> > >
> > >
> > > Currently in JdbcPOJOInsertOuput operator
Hi All,
Currently in JdbcPOJOInsertOuput operator we cannot configure JdbcFieldInfo
via properties.xml and the user has to do the necessary coding in his
application.
To start solving this issue I followed the steps mentioned on
http://docs.datatorrent.com/application_packages/#operator-propertie
Hi All,
The following stack trace is observed when we try to use XmlParser
Abandoning deployment due to setup failure.
java.lang.IllegalArgumentException
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:635)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:584)
at com.datatorr
[
https://issues.apache.org/jira/browse/APEXMALHAR-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2316:
--
Description:
Unable to set the tuple class attribute, getting the following stack
Hitesh Kapoor created APEXMALHAR-2316:
-
Summary: Cannot register tuple class in XmlParser Operator
Key: APEXMALHAR-2316
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2316
Project: Apache
Ramanath
wrote:
> Could Connection.getTransactionIsolation() be used to determine if
> transactions are supported ?
>
> Ram
>
> On Mon, Oct 24, 2016 at 8:08 AM, Hitesh Kapoor
> wrote:
>
> > Hi All,
> >
> > Need your views and suggestions regarding JdbcPO
standards.
Regards,
Hitesh Kapoor
Hi All,
It is observed that the exactly-once processing is not working correctly.
The reason for this is that when the operator crashes, it comes back and
inserts data again for non-checkpointed windows.
Hence redundant rows are added in the table. The fix is simple and
suggested by Sandeep is to
quot;COLUMN_NAME"));
> > }
> >
> > Example given here:
> > http://www.java2s.com/Code/Java/Database-SQL-JDBC/
> > GetColumnNameAndTypeForATable.htm
> >
> > 2. Execute the select statement putting a always false where clause like
> > "select * from t
turned by the select query to 1. I am using the JDBC
function setMaxRows() to achieve this.
Will be opening a PR for the same. This fix won't have corresponding unit
test cases and I will test the changes externally via an app.
Regards,
Hitesh Kapoor
[
https://issues.apache.org/jira/browse/APEXMALHAR-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568934#comment-15568934
]
Hitesh Kapoor commented on APEXMALHAR-2291:
---
Done
> Exact
[
https://issues.apache.org/jira/browse/APEXMALHAR-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2291:
--
Summary: Exactly-once processing not working correctly for
[
https://issues.apache.org/jira/browse/APEXMALHAR-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2290:
--
Summary: JDBC operator does not deploy in certain cases (was: JDBC
operator does
Hitesh Kapoor created APEXMALHAR-2291:
-
Summary: Exactly-once processing not working correctly
Key: APEXMALHAR-2291
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2291
Project: Apache Apex
Hitesh Kapoor created APEXMALHAR-2290:
-
Summary: JDBC operator does not deploy after failure in certain
cases
Key: APEXMALHAR-2290
URL: https://issues.apache.org/jira/browse/APEXMALHAR-2290
t (last
> commit
> > 4 days ago) and secondly this library has been used in Fixed Length File
> > Loader for Enrichment.
> >
> > My overall vote is to use univocity as much as possible and if there is
> any
> > missing (& important to us) feature in univocit
re-inventing the wheels and trying to make something robust can
> be
> > time consuming.
> >
> > -Chinmay.
> >
> >
> > On Wed, Sep 7, 2016 at 4:33 PM, Yogi Devendra <
> > devendra.vyavah...@gmail.com>
> > wrote:
> >
> > > Approac
[
https://issues.apache.org/jira/browse/APEXMALHAR-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2259:
--
Attachment: Mail_thread.pdf
> Create Fixed Length Parser Opera
[
https://issues.apache.org/jira/browse/APEXMALHAR-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Kapoor updated APEXMALHAR-2259:
--
Description:
An operator for parsing fixed width records has to be implemented
Hi All,
An operator for parsing fixed width records has to be implemented.
This operator shall be used to parse fixed width byte array/tuples based on
a JSON Schema and emit the parsed bytearray on one port; converted POJO
object on another port and the failed bytearray/tuples on an error port.
76 matches
Mail list logo
