The bug is a regression, so if it used to work with MSSQL and Oracle then
it will again. The fix is slated for the upcoming 0.6.0 release, and since
it has been reviewed and +1'ed, I'll be merging it into master shortly.
On Mon, Mar 7, 2016 at 9:52 AM, Ralf Meier wrote:
>
> Matt,
>
> thanks for
Matt,
thanks for the reply. Is this fix also solving the issue with Microsoft SQL
Server?
Is there estimation at which time such a fix is available for the public?
Thanks for your help.
BR
Ralf
> Am 07.03.2016 um 15:15 schrieb Matt Burgess :
>
> Unfortunately I don't think there is a workar
Unfortunately I don't think there is a workaround. The Oracle JDBC driver
does not return a table name for the result set [1]. Apparently some
drivers do (MySQL, DB2 e.g.) and some don't (Oracle). I have a fix on
GitHub for review [2].
Regards,
Matt
[1] https://community.oracle.com/thread/934039
Hi,
is there a possible solution for this issue?
I have the problem that I can’t use 0.4.0 through the fact that we need the
PutElasticSearch Processor which was introduced in 0.5.0.
It would be great if somebody could help here?
(By the way mysql is working)
BR
Ralf
> Am 05.03.2016 um 23:4
Hello Matt.
I've read about the new SQL processor that you are developing (
https://issues.apache.org/jira/browse/NIFI-1575) and is really Interesting.
I have started to work in the same idea for a new processor.
We developed a very similar Flume Source (
https://github.com/keedio/flume-ng-sql-sou
Sorry, not see that you are using MS SQL Server.
I deployed a host with MS SQL and the issue reproduces too.
My enviroment:
Nifi 0.5.1
Java 7
MS SQL Server 2008
With Oracle doesn't works too, but with DB2 works perfect.
2016-03-05 22:45 GMT+01:00 Marcelo Valle Ávila :
> Hello Ralf,
>
> I'm su
Hello Ralf,
I'm suffering the same behaviour, taking data from Oracle DB
failed to process due to org.apache.avro.SchemaParseException: Empty name
With NiFi 0.4.1 ExecuteSQL processor works fine, it seems that in 0.5.0 and
0.5.1 there is some bug with Oracle databases.
I test Nifi 0.5.1 process
Hi,
thanks Matt for clarifying things. I got it at the processor is working just
fine with mysql.
Now I tried to use it with MS SQL. But here I get some issues and could not
figure out why it is not working.
My Configuration is:
Nifi: 0.5.0
Java 8
MS SQL 2014
DBCPConnectionPool:
Database Con
Currently ExecuteSql will put all available rows into a single flow file.
There is a Jira case (https://issues.apache.org/jira/browse/NIFI-1251) to
allow the user to break up the result set into flow files containing a
specified number of records.
I'm not sure why you get 26 flow files, although i
Hi,
i tried to understand the executeSQL Processor.
I created a database with a table „users“. This table has two entries.
The problem with the processor is that it selected multiple times the entries
from the table and created altogether 26 flow files even that only two entries
where availab
10 matches
Mail list logo
