I have an index created by the JDBC river that contains types of objects:
Orders, Accounts etc.
If I execute the boosted multimatch query below I get back 50 of each type
of result. All is well.
However I'm trying to give the option to filter the list by user control
and lets say i only want
true;",
"sql":{
"callable" : true,
"statement" : "{call ESTransport(?)}",
"parameter" : "Entity"
},
"schedule":"0/30 0-59 0-23 ? * *",
"autocommit":true,
"index&q
2};
This is slick now it puts the brackets in and there is no escaping :-)
On Thursday, April 30, 2015 at 9:01:27 PM UTC-4, GWired wrote:
>
> I was able to get this to work in ES using head and got back what i needed.
>
> However translating to ElasticSearch.net has been an issue.
>
rt).
> the "best_fields" type will use the best score from the name, id, and _all
> searches. You might want most_fields to rank records that contain your
> query terms in name *and* id *and* other fields even higher. Note that
> my snippet is using the Query DSL. The syn
uot;:"jdbc",
"type":"Entity"
}
}
On Wednesday, April 29, 2015 at 7:42:33 AM UTC-5, Jörg Prante wrote:
>
> Nice work, can you share the recipe with the community?
>
> I could post it on the JDBC plugin wiki
>
> Jörg
>
> On Wed, Apr 29
is no method to resolve this within river logic.
>
> Jörg
>
>
> On Mon, Apr 20, 2015 at 2:11 PM, GWired > wrote:
>
>> I can't look at the feeder setup now but I could in the future.
>>
>> Is my SQL statement incorrect?
>>
>> Should I be doing
ill.
Thanks Garrett
On Thursday, April 23, 2015 at 2:48:03 AM UTC-4, Jörg Prante wrote:
>
> There are log messages at ES cluster side, you should look there why bulk
> indexing failed.
>
> Jörg
>
> On Thu, Apr 23, 2015 at 5:45 AM, GWired > wrote:
>
>> Found th
I am attempting to boost values for queries.
I'm searching across all fields and tables and returning 25 results for
each type.
This is working fine however I need to Boost if the field name Name or the
Field Name ID have the value in it.
I'm using ElasticSearchClient and sending this search.
Found this in the logs:
[2015-04-22 22:01:25,063][ERROR][river.jdbc.BulkNodeClient] bulk [15]
failed with 945 failed items, failure message = failure in bulk execution:
On Wednesday, April 22, 2015 at 7:53:25 PM UTC-5, GWired wrote:
>
> Hi All,
>
> I've just been informed t
Hi All,
I've just been informed that i'm off by up to 100k records or so in my jdbc
river fed index.
I am using the column strategy using a createddate and lastmodified date.
Kibana is reporting an entirely different # than what i see reported in the
DB..
Table A has 978634 in SQL, 934646 sh
I can't look at the feeder setup now but I could in the future.
Is my SQL statement incorrect?
Should I be doing something differently?
Does the river not utilize created_at and updated_at in this setup? I
don't have a where clause because I thought using the column strategy it
would take tha
I have a river created using the column strategy.
Whenever the system reboots or restarts it appears that the river is
forgetting it's last place and starts all over again.
These systems will do updates from time to time and rebuilding the indexes
is taking a really long time slowing down perfo
ading
> between the lines based on your hostname convention), then that is not
> recommended.
>
> The rest of your question is based on how you expect to grow, but until
> you get to more than 1 node you are probably going to have to restart your
> current one.
>
>
>
Is there a How to guide along with best practices for Scale Out?
I have a single instance server of Elastic Search and I would like to scale
out.
>From other posts in this group I have tried with no success to add an
additional server into the group.
This additional server is not on the same
Got it going as a service... ugh.. the user I was using didn't have rights
to run a service. Had to do it in the services.msc instead of service
manager.
On Thursday, January 29, 2015 at 10:09:46 PM UTC-5, GWired wrote:
>
> I've been messing with things on Host2 and it will no
20:44:57,804][INFO ][http ] [Cat]
bound_address
{inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.160.129.57:9200]}
[2015-01-29 20:44:57,805][INFO ][node ] [Cat] started
On Thursday, January 29, 2015 at 9:07:37 PM UTC-5, GWired wrote:
>
Can you gist/pastebin/etc your configs so we can check them?
>
> On 29 January 2015 at 14:56, GWired >
> wrote:
>
>> On my initial host (host1) I changed my cluster.name to
>>
>> cluster.name: ESMyName
>>
>> Which in elasticsearchhea
ome plugins need to be installed on all hosts
> regardless, so check the docs.
>
> On 27 January 2015 at 08:22, GWired >
> wrote:
>
>> Ok so I looked at the config file and found this:
>>
>> cluster.name - which you are saying I set it to the same on both
>
That was it, I guess Windows 8 has it out of the box.
On Tuesday, January 27, 2015 at 3:31:28 AM UTC-5, Akshay Davis wrote:
>
> Have you added the .json MIME type for the site in IIS?
>
>
>
> On Monday, January 26, 2015 at 3:46:44 PM UTC, GWired wrote:
>>
>> Yes,
n the ElasticSearch.net code that would allow me to
do some kind of discovery for nodes as well in the event one is down.
On Monday, January 26, 2015 at 3:34:04 PM UTC-5, GWired wrote:
> I'm doing this in windows.
>
> I'm crossing internal domains for each node so I thoug
something?
>
> Jörg
>
> On Mon, Jan 26, 2015 at 8:59 PM, GWired > wrote:
>
>> Is there a place where someone can point me to a simple set of
>> instructions for adding a node to an Elastic Search cluster?
>>
>> I think I understand Sharding and Nodes
Is there a place where someone can point me to a simple set of instructions
for adding a node to an Elastic Search cluster?
I think I understand Sharding and Nodes and that's what the documents do is
talk about them.
But what I don't understand is...
How do install ElasticSearch on the second
y 26, 2015 at 9:49:16 AM UTC-5, Magnus Bäck wrote:
> On Monday, January 26, 2015 at 14:58 CET,
> GWired > wrote:
>
> > I was able to get Kibana setup on my localhost and did a generic entry
> > to allow everything into the elasticsearch.yml
> > http.cors.allo
I was able to get Kibana setup on my localhost and did a generic entry to
allow everything into the elasticsearch.yml
http.cors.allow-origin: "/.*/"
Now I'm trying to getting it to run on my remote server running IIS 7.5 on
port 8080.
The page loads but only the top bar loads and nothing else
-> slaps forhead
oboe... hitpos should start at 0 not 1
got my results now converting to DG :-)
I will post final code once done.
On Tuesday, January 13, 2015 at 8:57:11 PM UTC-5, GWired wrote:
> Getting closer:
>
> I converted my searchResponse to a var
>
> i can now ref
Monday, January 12, 2015 at 10:37:00 PM UTC-5, GWired wrote:
> Ok that worked. Sort of. I can see the results in the response now.
>
> However I'm not able to refer to hits. I can see them but there isn't a
> hit or hits type to refer to so I can see what is in a hit.
26 matches
Mail list logo