profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/qdequele/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Quentin de Quelen qdequele Meili Paris CEO & Co-founder @meilisearch

Kerollmops/heed 161

A fully typed LMDB/MDBX wrapper with minimum overhead

Kerollmops/spo2 16

SpO₂ is oxygen saturation and is used in medical person monitoring.

qdequele/42sh 2

Simple an light command line

42Entrepreneurs/startup-school 1

This repo aims to centralize knowledge about startup-internship

baptistejamin/boulder-dash 0

Boulder Dash Clone using java

bidoubiwa/check-md 0

checks dead links of markdown

startedQovery/digital-mobius

started time in 6 days

startedbrunophilipe/Cakebrew

started time in 23 days

startedmas-cli/mas

started time in a month

issue commentmeilisearch/product

Analytics on SDKs/Integration usage

Hey, it's better to use a user agent. As custom headers could be removed by proxies, or requests with custom headers could be just trashed due to their custom header. I think it's better to avoid that by adding it, as required by the RFC in the User-Agent header. Today we are using a custom header for the X-Meili-API-Key instead of the Authorization official header, and we already had some issues with that.

gmourier

comment created time in a month

issue openedmeilisearch/product

Lao language support

Consider MeiliSearch support the Lao language. It seems that the word segmentation is not good and on the _matchesInfo the length of the words is not good (3 chars instead of 1 char).

How to reproduce

Data to insert:

[
  {
    "id": 1,
    "price": "3000000",
    "title": "ເຄື່ອງ ວັດ ແທກ ອຸນຫະພູມ",
    "location": "vientiane"
  },
  {
  "id": 2,
   "title": "Kingston SDCard 64GB + ພ້ອມສົ່ງ ອຸນຫະພູມ",
    "price": "100000",
    "location": "pakse"
  }
]

Search Query: http://127.0.0.1:7700/indexes/shop/search?q=%E0%BA%AD%E0%BA%B8%E0%BA%99&matches=true&attributesToHighlight=*&filters=location:pakse

Response:

{
   "hits":[
      {
         "id":2,
         "title":"Kingston SDCard 64GB + ພ້ອມສົ່ງ ອຸນຫະພູມ",
         "price":"100000",
         "location":"pakse",
         "_formatted":{
            "id":2,
            "title":"Kingston SDCard 64GB + ພ້ອມສົ່ງ ອຸນຫະພູມ",
            "price":"100000",
            "location":"pakse"
         },
         "_matchesInfo":{
            "title":[
               {
                  "start":32,
                  "length":9
               }
            ]
         }
      }
   ],
   "offset":0,
   "limit":20,
   "processingTimeMs":0,
   "query":"ອຸນ"
}

created time in a month

startedsanders41/meilisearch-python-async

started time in a month

issue commentmeilisearch/documentation

Table comparison with the competitors

Thanks @curquiza to bring back the topic on top of mind. We will take care of it with @gmourier in the next few days.

curquiza

comment created time in 2 months

release meilisearch/tokenizer

v0.2.4

released time in 2 months

created tagmeilisearch/tokenizer

tagv0.2.4

Library used by Meilisearch to tokenize queries and documents

created time in 2 months

delete tag meilisearch/tokenizer

delete tag : v0.2.4

delete time in 2 months

release meilisearch/tokenizer

v0.2.4

released time in 2 months

create barnchmeilisearch/tokenizer

branch : update-to-0.2.4

created branch time in 2 months

PullRequestReviewEvent
GollumEvent
GollumEvent
GollumEvent

delete branch meilisearch/product

delete branch : test

delete time in 2 months

create barnchmeilisearch/product

branch : test

created branch time in 2 months

PR opened meilisearch/specifications

Change the /version response

In the route /version the buildDate is now named commitDate and the format has changed

+4 -4

0 comment

1 changed file

pr created time in 2 months

create barnchmeilisearch/specifications

branch : fix-version-response

created branch time in 2 months

delete branch meilisearch/specifications

delete branch : fix-version-response

delete time in 2 months

PR closed meilisearch/specifications

Reviewers
Change the response on the /version route

In the route /version the buildDate is now named commitDate and the format has changed.

+10 -44

1 comment

1 changed file

qdequele

pr closed time in 2 months

PR opened meilisearch/specifications

Change the response on the /version route

In the route /version the buildDate is now named commitDate and the format has changed.

+10 -44

0 comment

1 changed file

pr created time in 2 months

create barnchmeilisearch/specifications

branch : fix-version-response

created branch time in 2 months

fork qdequele/examples

Community showcase and examples of Actix ecosystem usage.

fork in 2 months

issue closedmeilisearch/MeiliSearch

searching indexed arrays in the meiliesearch browser app not highlight correctly

Describe the bug When you have an index where an attribute is an array, it is returned in my laravel app but not in meilisearch's own browser.

To Reproduce Create an index where at least one field is an array. Search within the Meilisearch Browser for a string that is found within the array. Notice it is not highlighted as as with those results where the same string in found in a non-array attribute.

Expected behavior I expect the string within the array to highlight in the same way it does for non-array results.

Screenshots image MeiliSearch version: v0.20.0

closed time in 2 months

jayenne

issue commentmeilisearch/MeiliSearch

searching indexed arrays in the meiliesearch browser app not highlight correctly

Hello @jayenne, this issue is related to version 0.20 of MeiliSearch. It seems that it does not appear anymore in the new versions. So I will close this issue. Here is an example.

Screenshot 2021-07-19 at 16 49 48

You can see that in the field genres, the value Comedy has the highlight tags.

However, there are still some highlight problems introduced with version 0.21. These are described in issue #1480.

In case you manage to reproduce this bug in version 0.21, please reopen this issue.

Be careful, don't hesitate to look at the breaking changes in the releases to see the changes between v0.20 and v0.21. You can also find information in the article that explains the new features of v0.21.

jayenne

comment created time in 2 months

issue commentmeilisearch/MeiliSearch

v0.21 update status does not always return number of documents on document updates

Indeed I think it is a problem, thank you for pointing it out Charlotte. @gmourier I let you give your opinion and approve we want to keep the behavior on the v0.21. If it's approved, can @MarinPostma or @irevoire do it?

bidoubiwa

comment created time in 2 months

issue closedmeilisearch/MeiliSearch

V0.21 facetsDistribution attributes in search response are all lowercased

Describe the bug Previously we kept the casing of filters in facetsDistribution.

Given the following dataset:

[
  { "id": 1,    "title": "Alice In Wonderland",                    "author": "Lewis Carroll",            "genre": "Fantasy" }
]

and the following query:

/search?facetsDistribution=genres

The return is as follows:

{
    "hits": [
        {
            "id": 1,
            "title": "Alice In Wonderland",
            "author": "Lewis Carroll",
            "genre": "Fantasy"
        }
    ],
    "query": "alice in ",
//...
    "facetsDistribution": {
        "genre": {
            "fantasy": 1
        }
    },
    "exhaustiveFacetsCount": false
}

To Reproduce Steps to reproduce the behavior:

  1. Index the provided dataset
  2. Add genre in filterableAttributes
  3. Search with facetsDistribution = ["genres"]
  4. Casing lost in response

Expected behavior Keeping same casing

MeiliSearch version: v0.21.0

closed time in 2 months

bidoubiwa