I try to execute a simple flow with a MINFI CPP.
For now i create a random number and try to push this to a rest-api with invokehttp
in nifi it works perfectly, but in minifi it gives me the following error:
[class org::apache::nifi::minifi::utils::HTTPClient] [error] curl_easy_perform() failed Unsupported protocol on https://.......
what do i miss?
any hints?
thanks
stefan
Could you share what minifi-cpp version you are using? Is it a released binary or did you build it yourself? If you built it yourself, with what options? What platform do you use?
HTTPS support in minifi-cpp depends on how libcURL gets built: it can either be a system dependency, in which case HTTPS support depends on the system's libcURL, or it can be built-in, in which case OpenSSL support must be enabled (not disabled with OPENSSL_OFF and openssl-dev packages installed or the built-in OpenSSL enabled with USE_SYSTEM_OPENSSL=OFF).
The released 0.6.0 versions should support HTTPS on Linuxes, but I recall the Windows build having some problems with it.
Related
I am looking for an migration from assembla to jira, For this i need Ruby version 2.4.1(windows exe file) but i am unable to find it anywhere still now . can anyone share me the link. so, i will be able to complete my task.
Go to https://rubyinstaller.org/downloads/archives/ and download the version you want.
These are specifically for Windows users.
Looks like the v2.4.1 exe is https://github.com/oneclick/rubyinstaller2/releases/download/2.4.1-2/rubyinstaller-2.4.1-2-x64.7z
But if you’re OK with v2.4.10 - and I’d highly recommend that you try it, it will have security and big fixes which 2.4.1 lacks and will likely be compatible with anything which requires 2.4.x - then download this exe https://github.com/oneclick/rubyinstaller2/releases/download/RubyInstaller-2.4.10-1/rubyinstaller-devkit-2.4.10-1-x64.exe which includes the basic gems you’ll also need.
ALL,
In *nix, the usual way of building the software is to do:
../configure && make && make install
However sometimes you need to pass some options to configure. As an example you can say "../configure --prefix=".
Now sometimes configure has a lot of programmer defined options. As an example if I want to build a freeTDS software (driver to access MS SQL Server/Sybase Server) I can choose which DBMS I want to build against thru "--enable-mssql/--enable-Sybase".
Unfortunately I'm not very familiar with Xcode, however I do know that OSX is a type of *nix environment.
So my question is: do I have access to such configure options inside Xcode? Let's say I am building a software that uses ODBC. So I can use either unixODBC DM or iODBC DM. And so my thought is that I can use "--with-unixodbc/--with-iodbc" mutually exclusive configure options. But inside Xcode I have no idea where/how to define those.
Could someone please shed some light, please?
I have OSX 10.8 with the latest Xcode for that version, if it matters.
[EDIT]
On Linux when building pgodbc, I can use:
../configure --with-unixodbc=<some_dir>
or
../configure --with-iodbc=<some_dir>
Is there a way to tell Xcode I want to build with one OR another? Or you just build as many binaries as you wish?
Becase iODBC manager installs its files as a framework and unixODBC build from source installs as usual *nix file. So, when I build I want to know what I am testing against and what the user machine will have...
[/EDIT]
let's say the .proto files never changes, and we have a client -server system based on TCP, they speak each otehr via protobuf message. Before both client and server is on protobuf version 2.4.1. Now server upgrades to 2.5.0 (first recompile .java file using 2.5.0 protoc exe, than link against 2.5.0 runtime library). But client still work with 2.4.1 version. Can this system still work?
I think it is a common question for a client-server system. I believe it will work, but really I don't find any words about it from google offered document.
Yes, that should work fine. The only thing that would break it would be if you started using a new feature that doesn't exist in 2.4.1, but it would be impossible to do that without changing the .proto schema, so you are indeed safe against this. Version tolerance is a Big Thing in protobuf; new features (as an example: packed arrays) are always opt in and require .proto changes.
Can anyone help me for installation voltDB on MAC system i am trying to install it using instruction but get error
Cannot find config.m4.
Make sure that you run '/usr/bin/phpize' in the top level source directory of the module
I spent a couple of days to solve this issue google it get some post related to this error but not success to solve this issue, because i am new on MAC System so please help to install voltDB with Step by Step i'll very thankful
Installing VoltDB on a Mac uses the same process as on Linux.
The installation instructions are covered in Using VoltDB: Ch. 2: Installing VoltDB
If you are installing from the source code on Github, you first need to run a build. There are instructions to do this in Github on the project wiki.
However, from the error you are seeing, it looks like you are trying to compile the VoltDB PHP client library. To do that, I recommend downloading the PHP client library from VoltDB.com, since that includes both the PHP client library and the version of the C++ library that it depends on. It includes build instructions. If you're getting the source from github, you should know that the latest version of library is the native branch, not master.
I am trying to create a program using the postgresql database with lazarus.
I got the following error in compiling:
registersqldb.pas(72,3) Fatal: Can not find unit mysql55conn used by registersqldb.
what is wrong?
The project was probably created with a development version of FPC. (2.7.1 or 2.6.1), and you are probably trying to compile it with a stock release (2.6.0) version.
Solution: install a 2.6.1 based lazarus snapshot, or change the program to use an older mysql library.
I would recommend against 2.7.1 based snapshots. Too much is broken atm.
Disclaimer: I don't use mysql, so don't know exact compatibility details between versions, except that it is not always easy.