Hi,
Is it possible in DSE Cassandra Solr to search for JSON content within a
column?
We store a complex JSON in a column of type "text", very simplified version
below.
{
"userId": "user100",
"addressList": [{
"addressId": "100",
"address": "100 ABC Street"
}],
"userName": "user11"
}
In this,
er separator and use that for each leaf value of the nested
> tree.
>
> -- Jack Krupansky
>
> On Wed, Jan 13, 2016 at 11:40 PM, Joseph Tech <jaalex.t...@gmail.com>
> wrote:
>
>> Thanks, Field Transformers is exactly what i was looking for. Mine is a
>> some
; SELECT * FROM your_table WHERE solr_query='json:"*100 ABC Street*"';
>
> Warning: since you're storing in JSON format, searching data inside a JSON
> is equivalent to a wildcard seach *xxx* and it is quite expensive, even for
> full text search engines like Solr
&
h your own code/schema/table
> will help highlight what the difference is that causes the problem.
>
> Doc:
>
> http://docs.datastax.com/en/latest-dse/datastax_enterprise/srch/srchTrnsFrm.html
>
> -- Jack Krupansky
>
> On Fri, Mar 18, 2016 at 4:30 AM, Joseph Tech <jaalex.t...@gm
Hi,
I had setup a single-node DSE 4.8.x to start in Search mode to explore some
aspects of Solr search with field transformers (FT). Even though the
configuration seems fine and Solr admin shows the indexed data, and
searches on the actual fields (stored=true) work fine, but the FTs are not
being
hi,
I am facing an issue where Solr queries executed from cqlsh using the
solr_query field is throwing an NPE in system.log, while cqlsh shows the
following error:
Unable to complete request: one or more nodes were unavailable.
These queries work fine thru the Solr admin console UI.
Below is
work
<fieldInputTransformer* name="dse" *class="fqcn.of.XYZInputTransformer"/>
//works
Thanks,
Joseph
On Fri, Mar 18, 2016 at 9:33 PM, Joseph Tech <jaalex.t...@gmail.com> wrote:
> I had verified that it works on a 2-node cluster where one is setup as
> online,
Please check if nodetool getendpoints be used, if you know the key (going
by your problem description)
On 6 May 2016 22:04, "Siddharth Verma" wrote:
@Joseph,
An incident we saw in production, and have a speculation as to how it might
have occured.
*A detailed
Thanks, Eric. Just curious, at what point does the old sstables get deleted
from disk?
On Fri, May 6, 2016 at 8:41 PM, Eric Evans <john.eric.ev...@gmail.com>
wrote:
> On Fri, May 6, 2016 at 8:15 AM, Joseph Tech <jaalex.t...@gmail.com> wrote:
> > Please let me know how t
@Siddharth , is there any specific user case where this is required ; What
if the mainHost goes down?
On Fri, May 6, 2016 at 12:50 PM, Siddharth Verma <
verma.siddha...@snapdeal.com> wrote:
> Hi,
> Whitelist worked perfectly.
> Thanks for the help.
>
> In case, someone wants to use the same, the
Hi,
I am trying to get some baselines for capacity planning. The approach i
took was to insert increasing number of rows into a replica of the table to
sized, watch the size of the "data" directory (after doing nodetool flush
and compact), and calculate the average size per row (total directory
Hi,
Please let me know how to interpret the below output from cfstats,
especially the entry in bold.
SSTable count: 947
SSTables in each level: [1, 10, *104/100*, 832, 0, 0, 0, 0, 0]
We are using C* 2.0.14.459 (DSE version 4.6.7). and the table has been
created with :
cessing that occurs there - try removing this FOT and see if the NPE
> still occurs. For example, maybe the FOT is setting an output column value
> to NULL.
>
> Also, see if there is a "Caused By" entry elsewhere in the Java stack
> trace.
>
> -- Jack Krupansky
>
>
t; 5 digit ms times.
>
> The other place to look is your data model for that table if you want to
> post the output from a desc table.
>
> Patrick
>
>
>
> On Tue, Aug 30, 2016 at 11:07 AM, Joseph Tech <jaalex.t...@gmail.com>
> wrote:
>
>> On furth
umber of triplets: (name, value, timestamp)
>
> Also, I see that you have set sstable_size_in_mb at 50 MB. What is the
> rational behind this? (Yes I'm curious :-) ). Anyway your "SSTables per
> read" are good.
>
> Best,
>
> Romain
>
> Le Lundi 5 septembre 2016
> Regard,
>
> Ryan Svihla
>
> _
> From: Joseph Tech <jaalex.t...@gmail.com>
> Sent: Wednesday, August 31, 2016 11:16 PM
> Subject: Re: Read timeouts on primary key queries
> To: <user@cassandra.apache.org>
>
>
>
> Patrick,
>
> The
partition keys have less than (or equal to) 1109
>> cells.
>> You can see these data of a given sstable with the tool sstablemetadata.
>>
>> Best,
>>
>> Romain
>>
>>
>>
>> Le Lundi 5 septembre 2016 15h17, Joseph Tech <jaalex.t...@gmail.co
(1000).build();
>cluster.register(queryLogger);
>
> Then in your driver logback file:
>
> level="DEBUG" />
>
> *3) *And/or: you mentioned that you use DSE so you can enable slow
> queries logging in dse.yaml (cql_slow_log_options)
>
r*
> *M*: +91 8447784271 *T*: +91 124-415-6069 *EXT*: 12369
> Plot # 362, ASF Centre - Tower A, Udyog Vihar,
> Phase -4, Sector 18, Gurgaon, Haryana 122016, INDIA
>
> On Tue, Aug 30, 2016 at 5:10 PM, Joseph Tech <jaalex.t...@gmail.com>
> wrote:
>
>> Hi Patrick,
>&g
LOCAL_QUORUM might point to a datacenter mis-match
> on node count + RF.
>
> What does your nodetool status look like?
>
> Patrick
>
> On Mon, Aug 29, 2016 at 10:14 AM, Joseph Tech <jaalex.t...@gmail.com>
> wrote:
>
>> Hi,
>>
>> We recently started gettin
ead?
Thanks,
Joseph
On Wed, Sep 7, 2016 at 5:26 PM, Joseph Tech <jaalex.t...@gmail.com> wrote:
> Thanks, Romain for the detailed explanation. We use log4j 2 and i have
> added the driver logging for slow/error queries, will see if it helps to
> provide any pattern once in
Hi,
Below is a sample trace for a LOCAL_QUORUM query . I've changed the query
table/col names and actual node IP addresses to IP.1 and IP.coord (for the
co-ordinator node). RF=3 and we have 2 DCs. Don't we expect to see an
"IP.2" since LOCAL_QUORUM requires the co-ordinator to receive at least 2
s not your case.
> So you're right the coordinator should have sent a digest request to
> another node.
> Did you executed this request with cql ? Are you sure you have correctly
> set the consistency before executing the request ?
>
> --
> Nicolas
>
>
>
> Le j
Hi,
We recently started getting intermittent timeouts on primary key queries
(select * from table where key=)
The error is : com.datastax.driver.core.exceptions.ReadTimeoutException:
Cassandra timeout during read query at consistency LOCAL_QUORUM (2
responses were required but only 1 replica
a
24 matches
Mail list logo