[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568537#comment-15568537
]
Chaitanya commented on APEXMALHAR-2284:
---
Able to reproduce the issue. It's happ
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
Projec
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 M
[
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 n
[
https://issues.apache.org/jira/browse/APEXMALHAR-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568904#comment-15568904
]
Sandesh commented on APEXMALHAR-2291:
-
Can you please update the title with the o
Sandesh created APEXCORE-556:
Summary: New operator attribute - RECOVERY_WINDOW_COUNT
Key: APEXCORE-556
URL: https://issues.apache.org/jira/browse/APEXCORE-556
Project: Apache Apex Core
Issue Typ
[
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
JdbcPOJOInsertOutputOper
[
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
> Exactly-once processin
Hi All,
This issue occurs when we try to insert records in a table which has a lot
of data.
The setup method of JdbcPOJOInsertOutputOperator generates the metadata of
the columns in the table. To do so it fires a query of the form "Select *
from tablename" and the extracts the required meta data l
GitHub user Hitesh-Scorpio opened a pull request:
https://github.com/apache/apex-malhar/pull/452
APEXMALHAR-2290 Changes for JDBC populate metadat will fetch only 1 row
@bhupeshchawda @chinmaykolhatkar please review
You can merge this pull request into a Git repository by running:
[
https://issues.apache.org/jira/browse/APEXMALHAR-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568993#comment-15568993
]
ASF GitHub Bot commented on APEXMALHAR-2290:
GitHub user Hitesh-Scorpio o
[
https://issues.apache.org/jira/browse/APEXCORE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569056#comment-15569056
]
Thomas Weise commented on APEXCORE-556:
---
The assumption that operators need (signi
[
https://issues.apache.org/jira/browse/APEXCORE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569136#comment-15569136
]
Sandesh commented on APEXCORE-556:
--
One example is in Kafka 0.9 Exactly once output ope
[
https://issues.apache.org/jira/browse/APEXMALHAR-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569248#comment-15569248
]
Siyuan Hua commented on APEXMALHAR-2283:
There are couple of solutions to "ex
GitHub user prasannapramod reopened a pull request:
https://github.com/apache/apex-malhar/pull/447
Fixed GenericFileOutputOperator rotateCall
@yogidevendra please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prasannapram
Github user prasannapramod closed the pull request at:
https://github.com/apache/apex-malhar/pull/447
---
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 fe
A JIRA has been created for adding this thread affinity check
https://issues.apache.org/jira/browse/APEXCORE-510 . I have made this
enhancement in a branch
https://github.com/sanjaypujare/apex-core/tree/malhar-510.thread_affinity
and I have been benchmarking the performance with this change. I will
Hi Hitesh,
Instead of limiting the row count please use one of the following 2
approaches:
1. ResultSet rsColumns = null;
DatabaseMetaData meta = conn.getMetaData();
rsColumns = meta.getColumns(null, null, "tablename", null);
while (rsColumns.next()) {
System.out.println(rsColum
In case there turns out to be a penalty, we can introduce a "check for
thread affinity" mode that triggers this check. My initial thought is to
make this check ON by default. We should wait till benchmarks are available
before discussing adding this check.
Thks
Amol
On Wed, Oct 12, 2016 at 11:07
[
https://issues.apache.org/jira/browse/APEXCORE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569606#comment-15569606
]
Munagala V. Ramanath commented on APEXCORE-556:
---
The `AbstractFileInputOpe
Looks like there is objection with the changes so we will go ahead and
merge it.
On Mon, Oct 10, 2016 at 8:40 PM, Thomas Weise wrote:
> I just submitted a PR to correct the meetup link on the community page and
> fit it into a broader "Events" section. The intention is to link to meetup
> group
Github user asfgit closed the pull request at:
https://github.com/apache/apex-site/pull/56
---
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 en
There is *no* objection with the changes. :)
I have merged it.
On Wed, Oct 12, 2016 at 1:27 PM, Thomas Weise wrote:
> Looks like there is objection with the changes so we will go ahead and
> merge it.
>
>
> On Mon, Oct 10, 2016 at 8:40 PM, Thomas Weise wrote:
>
> > I just submitted a PR to corr
[
https://issues.apache.org/jira/browse/APEXMALHAR-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569872#comment-15569872
]
Thomas Weise commented on APEXMALHAR-2283:
--
The operator recovery assumes th
[
https://issues.apache.org/jira/browse/APEXMALHAR-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2283:
-
Summary: Issues with Kafka output operator (was: Refactor kafka output
operator)
>
Probably should be accessible to PMC and/or committers only for now. If the PMC
wants to allow sharing this data with other 3rd parties, then the privacy
message will need to be changed.
Additionally, the website may need a privacy footer to indicate metrics are
being collected.
Please take a
GitHub user mx4web opened a pull request:
https://github.com/apache/apex-site/pull/57
APEXCORE-514 Further navigation changes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mx4web/apex-site apexcore-514.apexwebsite
Alternativel
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570194#comment-15570194
]
ASF GitHub Bot commented on APEXCORE-514:
-
GitHub user mx4web opened a pull requ
Github user asfgit closed the pull request at:
https://github.com/apache/apex-site/pull/57
---
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 en
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved APEXCORE-514.
---
Resolution: Done
> Apache Apex website update
> --
>
>
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570218#comment-15570218
]
ASF GitHub Bot commented on APEXCORE-514:
-
Github user asfgit closed the pull re
GitHub user tweise opened a pull request:
https://github.com/apache/apex-site/pull/58
APEXCORE-514 Remove Announcements, add Events under Community.
@davidyan74 review/merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tweise/a
[
https://issues.apache.org/jira/browse/APEXCORE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570417#comment-15570417
]
ASF GitHub Bot commented on APEXCORE-514:
-
GitHub user tweise opened a pull requ
[
https://issues.apache.org/jira/browse/APEXCORE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Chandra Putta updated APEXCORE-553:
--
Description:
Add Google Analytics tracking to the apex.apache.org website so t
I run jmh test and check takes 1ns on my MacBook Pro and on the lab
machine. This corresponds to 3% degradation at 30 million events/second.
I think we can move forward with the check ON by default. Do we need an
ability to turn OFF check for a specific operator and/or port? My
thought is that
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570783#comment-15570783
]
Chinmay Kolhatkar commented on APEXMALHAR-2284:
---
Changing priority to a
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kolhatkar updated APEXMALHAR-2284:
--
Priority: Blocker (was: Major)
> POJOInnerJoinOperatorTest fails in Travis
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570783#comment-15570783
]
Chinmay Kolhatkar edited comment on APEXMALHAR-2284 at 10/13/16 4:19 AM:
--
+1 for ON by default
+1 for disabling it for all output ports
With the kind of issues we have observed being faced by developers in the
past, I strongly believe this check should be ON by default.
However at the same time I feel, it shall be one-time check, mostly in
Development phase and before g
+1 for on by default and ability to turn it off for entire application.
- Tushar.
On Thu, Oct 13, 2016 at 11:00 AM, Pradeep A. Dalvi wrote:
> +1 for ON by default
> +1 for disabling it for all output ports
>
> With the kind of issues we have observed being faced by developers in the
> past, I s
+1 for Option 1 to use conn.getMetaData()
--prad
On Wed, Oct 12, 2016 at 11:39 PM, Chinmay Kolhatkar
wrote:
> Hi Hitesh,
>
> Instead of limiting the row count please use one of the following 2
> approaches:
>
> 1. ResultSet rsColumns = null;
> DatabaseMetaData meta = conn.getMetaData();
>
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571020#comment-15571020
]
Chaitanya commented on APEXMALHAR-2284:
---
This was failing due to the below merg
Vlad,
I agree that the check should be ON by default. Ability to turn it off for
entire app is fine, per port is not needed.
Thks
Amol
On Wed, Oct 12, 2016 at 10:34 PM, Tushar Gosavi
wrote:
> +1 for on by default and ability to turn it off for entire application.
>
> - Tushar.
>
>
> On Thu, Oct
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571020#comment-15571020
]
Chaitanya edited comment on APEXMALHAR-2284 at 10/13/16 6:46 AM:
--
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571074#comment-15571074
]
Chandni Singh commented on APEXMALHAR-2284:
---
Are you sure about that?
The
[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571074#comment-15571074
]
Chandni Singh edited comment on APEXMALHAR-2284 at 10/13/16 6:57 AM:
--
46 matches
Mail list logo
